Leecode_SQL50_1661. Average Time of Process per Machine

Leecode_SQL50_1661. Average Time of Process per Machine

Problem description

Table: Activity

±---------------±--------+

| Column Name | Type |

±---------------±--------+

| machine_id | int |

| process_id | int |

| activity_type | enum |

| timestamp | float |

±---------------±--------+

The table shows the user activities for a factory website.

(machine_id, process_id, activity_type) is the primary key (combination of columns with unique values) of this table.

machine_id is the ID of a machine.

process_id is the ID of a process running on the machine with ID machine_id.

activity_type is an ENUM (category) of type ('start', 'end').

timestamp is a float representing the current time in seconds.

'start' means the machine starts the process at the given timestamp and 'end' means the machine ends the process at the given timestamp.

The 'start' timestamp will always be before the 'end' timestamp for every (machine_id, process_id) pair.

It is guaranteed that each (machine_id, process_id) pair has a 'start' and 'end' timestamp.

There is a factory website that has several machines each running the same number of processes. Write a solution to find the average time each machine takes to complete a process.

The time to complete a process is the 'end' timestamp minus the 'start' timestamp. The average time is calculated by the total time to complete every process on the machine divided by the number of processes that were run.

The resulting table should have the machine_id along with the average time as processing_time, which should be rounded to 3 decimal places.

Return the result table in any order.

The result format is in the following example.

Example 1:

Input:

Activity table:

±-----------±-----------±--------------±----------+

| machine_id | process_id | activity_type | timestamp |

±-----------±-----------±--------------±----------+

| 0 | 0 | start | 0.712 |

| 0 | 0 | end | 1.520 |

| 0 | 1 | start | 3.140 |

| 0 | 1 | end | 4.120 |

| 1 | 0 | start | 0.550 |

| 1 | 0 | end | 1.550 |

| 1 | 1 | start | 0.430 |

| 1 | 1 | end | 1.420 |

| 2 | 0 | start | 4.100 |

| 2 | 0 | end | 4.512 |

| 2 | 1 | start | 2.500 |

| 2 | 1 | end | 5.000 |

±-----------±-----------±--------------±----------+

Output:

±-----------±----------------+

| machine_id | processing_time |

±-----------±----------------+

| 0 | 0.894 |

| 1 | 0.995 |

| 2 | 1.456 |

±-----------±----------------+

Explanation:

There are 3 machines running 2 processes each.

Machine 0's average time is ((1.520 - 0.712) + (4.120 - 3.140)) / 2 = 0.894

Machine 1's average time is ((1.550 - 0.550) + (1.420 - 0.430)) / 2 = 0.995

Machine 2's average time is ((4.512 - 4.100) + (5.000 - 2.500)) / 2 = 1.456

My solution

sql 复制代码
WITH st AS (
    SELECT machine_id, process_id, timestamp
    FROM Activity
    WHERE activity_type = 'start'
), 
en AS (
    SELECT machine_id, process_id, timestamp
    FROM Activity
    WHERE activity_type = 'end'
), 
b AS (
    SELECT st.machine_id, st.process_id, (en.timestamp - st.timestamp) AS time_taken
    FROM st 
        JOIN en 
            ON st.machine_id = en.machine_id 
            AND st.process_id = en.process_id
)

SELECT b.machine_id, ROUND(AVG(time_taken), 3) AS processing_time
FROM b
GROUP BY b.machine_id

Other solutions

sql 复制代码
select a1.machine_id, round(avg(a2.timestamp-a1.timestamp), 3) as processing_time 
from Activity a1
	join Activity a2 
		on a1.machine_id=a2.machine_id 
			and a1.process_id=a2.process_id
			and a1.activity_type='start' 
			and a2.activity_type='end'
group by a1.machine_id
sql 复制代码
Select a.machine_id,ROUND(AVG(b.timestamp-a.timestamp), 3)as processing_time 
from Activity a, Activity b
where a.process_id=b.process_id 
	AND a.machine_id=b.machine_id
	AND a.activity_type="start" 
	AND b.activity_type="end"
group by machine_id;
相关推荐
海兰6 小时前
【数据库】tdsql(mysql8.0)优化思考三
数据库·redis
煎饼学大模型7 小时前
Agent 的“大脑-手“解耦架构:当推理层和工具执行层各自独立演进
数据库·人工智能·oracle·架构·agent
Lucifer三思而后行8 小时前
Veeam 备份 Oracle RAC 失败,是归档删除脚本的锅!
sql
muddjsv11 小时前
SQLite数据库文件机制详解:journal、wal、shm文件作用与备份避坑
数据库·sqlite
吴声子夜歌12 小时前
MongoDB 4.2——应用程序设计
数据库·mongodb
数字新视界12 小时前
动环监控可视化在数据中心管理中的应用与实践解析
数据库·物联网·解决方案·动环监控·大榕树
极地野狼 音乐哔哔12 小时前
数据库备份恢复的原理实践
数据库
互联网中的一颗神经元12 小时前
小白python入门 - 25. SQL 与表设计入门
数据库·python·sql
ttwuai12 小时前
AI 生成后台改数据后,操作日志别只记按钮:Go + MySQL 怎么验
数据库·人工智能·mysql·golang
KaMeidebaby13 小时前
卡梅德生物技术快报 | 核酸适配体文库测序:核酸适配体文库测序的技术原理、实验流程与数据解析
前端·网络·数据库·人工智能·算法