On Wed, Nov 30, 2011 at 7:41 PM, KlenPJ hopIJQy <[email protected]>wrote:
> Usability is the most biggest problem of Pylons Pyramid. > > I am newer to Pylons Pyramid. i am care about the usability. > > when we want to built a biggest heavily load website , we care about how > could we handler the heavily request. > > but via pyramid document, we could not find out the right answer. > > what ever the code write , it needs to be running on the real server. > > we should focus on the real world. > > > i need real tech white paper about how to built high load website. such > as a hot online trade site, a hot forum, a hot web game. > > Pyramid is built with speed in mind and is really quick for the things it does but it stays out of your way and lets you make your own decisions. If you need to build a highly scalable application, pyramid is a good choice, but you will have to do a little research and make the right decisions when building it. Things you should look at: Template Engine Performance: Jinja2 vs Mako vs Genshi vs Chameleon Database Performance: MySQL vs Postgres vs NoSQL Options (Mongo, Redis Cassandra) Caching and Indexing: Beaker, Memcached, Solr, Vagrant Webservers: Gunicorn, Apache, Gevent Queueing Long Running Processes: cron, celery, zmq, gevent All these decisions truly depend on your needs and the application you are building and that is why Pyramid stays out of your way and why one single white paper wouldn't really be that helpful. If you want to get more detailed with what you are building and the needs of the application we might be able to outline some best practices and help you make the right decisions though. -- 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.
