On Sat, Nov 6, 2010 at 4:51 AM, miniwark <[email protected]> wrote: > - Frightened because i am near to finish a Pylons 1 project, and i > already "lost" a lot of time during the process (choising betwinf > Django/TG2/Pylons, then making Auth
Have no fear, most of us are in the same position. We're working on Pylons 1 applications now, and/or we're running 1 or 0.9.7 applications. Some of these we'll upgrade to Pyramid over the year after release, and others we'll just keep running at the same version until the app is retired. So among all Pylons users, that's a lot of applications running in all three versions. Pylons has been under development for five years. Most of the production bugs have been ironed out. Only a handful of major bugs have been reported each year since 0.9.7 was released three (?) years ago, and few if any of these caused an otherwise-happy production application to crash or misbehave. At worst a security vulnerability is discovered, a new version of Pylons or Routes is released to fix it, users upgrade the package, and nothing breaks. 99% of bugs and difficulties occur during development or in the first month after rollout. The most common problem a few Pylons users report in production is not bugs but memory. Some people have reported problems with cheap webhosts offering 256M or 512 MB servers. Just use a server with 1 GB of RAM and expandable, and you can avoid these issues. Here's my current memory usage with five apps as reported by ps. The first number is virtual memory, the second physical. Some of it is shared between processes but it's hard to tell how much. App 1: 475 MB / 175 MB (highest usage, large db records) App 2: 279MB / 38MB (small app, quasi-static pages) App 3: 327 MB / 83MB (two big data structures in memory) App 4: 471 MB / 116 MB (large internal downloads) App 5: 335 MB / 60 MB (most intense read/write db) -- Mike Orr <[email protected]> -- 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.
