vdbergh

Results 434 comments of vdbergh

get_machines is too slow and does not use the book keeping data

And as I said, an additional enhancement could be to recreate the list every minute in a scheduled task (rather than creating it on demand).

get_machines is too slow and does not use the book keeping data

Note that the `wtt_map` itself may contain some inactive tasks (avoiding this clutters the code too much IMHO). These inactive tasks are evicted in a scheduled task that runs every...

get_machines is too slow and does not use the book keeping data

Well I do not know where the bottleneck is. It could also be in mako. Currently the table is computed on demand but there is a delay (of the order...

get_machines is too slow and does not use the book keeping data

I do not know how much time it takes to generate the html from the data structure. If it takes 1s and 60 people want to view the machines lists...

get_machines is too slow and does not use the book keeping data

The wtt_map is always up to date (except that it contains some inactive tasks which are periodically cleaned). But you still need to generate the html from it. That's what...

get_machines is too slow and does not use the book keeping data

Perhaps I should clarify that the `wtt_map` was not created to support the machine list, but to very efficiently detect duplicate workers (even when Vondele's fleet is visiting). For the...

get_machines is too slow and does not use the book keeping data

The thing is that I am not 100% sure that generating the data is the bottleneck. I wonder if it is not the generation of a table with > 15000...

get_machines is too slow and does not use the book keeping data

I guess we could try. But it would require a fleet visit to see the effect.

get_machines is too slow and does not use the book keeping data

Well it takes more than 15min to implement this...

get_machines is too slow and does not use the book keeping data

> Good thing the fleet is visiting right this very moment :) (the server is even holding fairly steady at 100+k cores for two hours now!) Yes the server seems...