haiyangding

Hi, sorry for the confusion. All values are normalized between [0, 100], not [0, 1]. That said, 100 means the memory is equal to the capacity of the machine.

> Thanks for the clarification for `plan_mem`. I also observed 50 within `plan_cpu`. We could also observe 5, 12, or 60 in batch_task.csv > > task_MzQwMDQzNjY0MzkwNzU2ODYyMg==,2511,j_424759,9,Terminated,366991,372325,60,0.39 > task_ODg3NTU4NTE3NDcxODA4NjA5Ng==,168,j_366800,3,Terminated,466234,467613,12,1.57 > >...

I would try to clarify this by answering your questions: > so the "Waiting" tasks mean that they are waiting for other tasks finishing ? No. A task is "Waiting"...

Hi, thanks for pointing the errors in the doc and I will update them. Now to your questions. 1. About the normalization of mem_gps. All values in mem_gps (aka memory...

Hi, maximum value of the mem_gps is "a constant value across all trace data", everything should be fine. Let me know if you had any further concern/question :)

https://stackoverflow.com/questions/3073948/job-task-and-process-whats-the-difference/31212568 Here is a link I found via Google. Basically, the job-task-instance model is applied in many distributed computing frameworks but the word may vary.

Yes, the actual resource used can be larger than that the task has requested. This is an example of over-subscription. As for (some of) the batch tasks, it can be...

> > Yes, the actual resource used can be larger than that the task has requested. This is an example of over-subscription. > > As for (some of) the batch...

Our containers are running on both physical machines and VMs.

Hi, trace v2018 covers some machine properties but not all of what mentioned here. We could consider adding them in the next version. Sorry for the inconvenience.