so, how about using the performance (response times) of an app server as fitness functions for a population of configuration properties sets that tune an application (heck, through in the app's DB too) running on that server...
for extra credit, write the code gen utility that parses the application's pages and introspects the app server's classes for tunable bottlenecks (maybe it finds places to insert a queueing interface or an object pool) makes adjustments to the architecture as necessary, sets up timing triggers, configures the genetic algorithim, generates the first population of config files, and iteratively launches the application under one individual against a load test tool....
ok, so its not the Internet at large, still, it could be fun!
Slashdot Mirror
for extra credit, write the code gen utility that parses the application's pages and introspects the app server's classes for tunable bottlenecks (maybe it finds places to insert a queueing interface or an object pool) makes adjustments to the architecture as necessary, sets up timing triggers, configures the genetic algorithim, generates the first population of config files, and iteratively launches the application under one individual against a load test tool....
ok, so its not the Internet at large, still, it could be fun!