On Sunday, January 9, 2011 6:05:16 PM UTC+11, Massimo Di Pierro wrote: > > Graham. We all appreciate your expertise here and appreciate people > who say what they think. Perhaps diplomacy is not our strength. You do > not need to justify your tweet. I though it was funny because - in my > view - it would apply equally well to some of the other frameworks. >
Yes, there is at least one other web framework which I find a bit annoying as far as people associated with it pushing that their viewpoint is the best. They generally keep to themselves though. And no that other framework isn't Django. I have always found people in Django community quite open and pleasant to deal with and I wouldn't take the momentary frustrated outbursts of one individual as saying too much about the community as a whole. No matter what the framework, one can always come across specific individuals which are quite extreme in their views and try to monopolise a situation and so can be difficult to deal with. I am sure you have possibly seen that at times on the Python WEB-SIG. I am even guilty of it some times, especially when I have got frustrated because of stuff being hijacked all the time. :-( Graham > On Jan 9, 12:24 am, Graham Dumpleton <graham.d...@gmail.com> > wrote: > > On Sunday, January 9, 2011 3:54:37 PM UTC+11, Anthony wrote: > > > > > Graham, welcome. Careful, though -- we might convert< > http://twitter.com/GrahamDumpleton/status/23120780938190848>you. ;-) > > > > >http://twitter.com/GrahamDumpleton/status/23120780938190848 > > > > I have been posting here for quite a long time actually and tried a few > > times to get Massimo to temper his ways but even though he is more > > restrained now, sorry to say, he does still seem to rub people up the > wrong > > way as do the reactions of others in the web2py community. You guys > really > > just got to learn to do your own thing and not treating it like a crusade > > > where you have to convert the world. Django became popular on technical > > merit and because of easily accessible good documentation, not because > its > > community went around like <insert name of church group> knocking on > doors > > trying to convert people or arguing every little minor technical point to > > > try and win people other. That sort of behaviour really reminds me of > some > > new age christians I have known in the past who just could not shut up in > > > trying to make you believe what they believed. It gets tiresome and > > sometimes one cant take any more and gets angry about having your time > > wasted. I can therefore appreciate the reactions of others associated > with > > other web frameworks, and if you think the latest outburst about imports > was > > some reaction about web2py getting a tutorial accepted in PyCon as some > like > > to think, you are very sadly mistaken. They are more likely just a > > manifestation of this frustration of having web2py shoved in your face > one > > too many times especially when muds gets thrown in your direction. So, > quiet > > it down and you will go a lot further with less angst against you. > > > > FWIW, although I find some of the ways web2py does things an interesting > > approach and would be appealing to certain classes of users, I do have > > concerns about how it does other things, especially in conjunction with > how > > it tries to label itself an enterprise framework. So, it definitely isn't > in > > my mind suitable for all situations. As to the 'import' issue, I don't > give > > a stuff about it either way so please don't drag me into that one. > > > > Graham > > > > > > > > > > > > > > > > > > > > > On Saturday, January 8, 2011 10:59:37 PM UTC-5, Graham Dumpleton wrote: > > > > > >> You were possibly using a an old version of sqlite which isn't safe to > use > > >> in a multithreaded configuration. > > > > >> The MPM settings are not going to help in this case as that error > could > > >> only come about because you are using mod_wsgi daemon mode and so > > >> application is running in distinct process and not those affected by > the MPM > > >> or its settings. > > > > >> The only other way you could get that error is that you are actually > > >> running web2py as a CGI script. > > > > >> Overall, that specific error message means your daemon mode process > that > > >> is running web2py crashed. You would likely find that there is a > > >> segmentation fault messages in main Apache error log as well at that > time. > > > > >> Crashing could be because of sqlite thread problems, but could also be > > > >> because you are forcing web2py to run in main interpreter of daemon > > >> processes and at the same time are using a third party C extension > module > > >> for Python that is not safe for use in sub interpreters. > > > > >> So, ensure sqlite is up to date. And ensure that you have: > > > > >> WSGIApplicationGroup %{GLOBAL} > > > > >> in configuration to force use of main interpreter. > > > > >> Graham > > > > >> On Sunday, January 9, 2011 6:44:14 AM UTC+11, VP wrote: > > > > >>> We occasionally got an Apache error so the page didn't get displayed. > > > >>> So I decided to stress test using Apache Bench (ab). It seems the > > >>> site suffered failure up to 50-100 concurrent connection. > > > > >>> Apache error log showed this error: > > > > >>> >>>>>>Premature end of script headers: wsgihandler.py > > > > >>> After digging around, I found similar discussions and change > > >>> apache2.conf like this: > > > > >>> # prefork MPM > > >>> StartServers 5 > > >>> MinSpareServers 5 > > >>> MaxSpareServers 10 > > >>> MaxClients 256 > > >>> MaxRequestsPerChild 500 > > >>> ServerLimit 256 > > > > >>> Didn't seem to help. > > > > >>> ==== > > > > >>> A few notes: > > > > >>> + It appears when I switched to sqlite instead of posgres, I didn't > > >>> have the problem. (Sqlite had other problems, such as occasional > > >>> database locking, which is more serious) > > > > >>> + I am on a VPS with 768MB with 1GB burstable. While I'm doing the > > >>> stress test with Apache Bench (ab), using free on the server revealed > > > >>> memory usage was about 450MB. (Which is a lot, but is still under > > >>> limit). > > > > >>> ===== > > > > >>> In summary, memory was available. But we got this wsgi error in > > >>> Apache with multiple requests. > > > > >>> Any idea please? > > > > >>> Thanks.
