[snip] > You have to be doing a lot of systems, but some actions can take a > minute or more per system on a loaded satellite. There's some pl/sql > that needs optimizing me thinks...
I haven't looked into the base channel changing, but you can see some of the numbers before and after my child channel changing optimizations here: https://bugzilla.redhat.com/show_bug.cgi?id=469984 I understand deleting a server is a really painful operation as well. > so engineering a solution that will > allow operations that are taking days is the wrong thing to fix IMO :) I completely agree, but that's not the idea. Inevitably larger amounts of systems take longer, so I think making them async in general makes sense. But the second step is revisiting a lot of these implementations. From what I've seen, the approach seems to be doing the same thing as for single servers, just multiple times. There's a lot of room for caching results across the batch as well as some more creative ways of tuning for multiple systems. -- Jason Dobies ([email protected]) RHN Satellite & Spacewalk RHCE# 805008743336126 Freenode: jdob @ #spacewalk, #spacewalk-devel _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
