Thanks for the prompt response! There are two points that may help:

• Please check the leftmost timestamp for the evaluation speed. Note that "Wall clock" is the FL runtime simulated using realistic FL trace;
• Please double check whether you have fedscale driver stop $JOB_NAME before submitting a new job. Otherwise, concurrent jobs lead to resource contention, thus slower evaluation;
• Please consider to use overcommitment > 1 (in real FL it is often set to 1.3) when we are activating device_trace in configs. This is because FedScale will integrate the client availability trace after specifying the device_trace. So the number of completion we will receive will be slightly smaller than the number of participants we selected, but overcommitment > 1 will ensure we are selecting more clients. e.g., check the "Succeed participants:" vs. "Planned participants" in these two figures. If you don't care about realistic client availability, just comment out device_trace.

Hope this can help. Thank!

Thank you very much. I will check my code carefully again!