With stuff like this, you'll definitely get a productivity increase by using nginx/lighttpd in front of Pylons -- the server on front can be configured to pull in the entire file from the client & caching before passing off to nginx.
Something that I would bring up though - is what are you doing with these files ? And have you been able to test your code to see if the bottleneck is elsewhere ? I can see a few issues causing this: - KeepAlive / Persistent connection settings - are you doing an http open/close for every file ? that will slow stuff down - disk io - lots of little files use more resources than fewer little files. your applications design/architecture might be running into issues because of this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
