Is the GWC seed page simply a web frontend for the REST API of Geoserver?
Is there another option for submitting requests to the underlying GWC/Geoserve?
I have some scripts that need to whack away at a local Geoserver instance with the REST api but I've come to the conclusion it is leaving lots of performance on the floor. I suspect it's related to the entire network/REST protocol stack taking a significant portion of the CPU cycles.
Greg