I noticed a funny thing with my TG SQLite demo today. I've been getting spotty performance. Some days a search page takes 4 seconds to list its results; other days it takes 55 seconds for the same search. And right now it won't do anything except hang. So I ran 'lsof' to see if some other program had the database open and it was waiting for a lock. A pageful of TurboGears threads were running. Funny because I'd quit it. I killed them and restarted the server.
Then I discovered if the server is not handling a request, pressing ctrl-C quits all the threads. But if it is handling a request, the threads remain. If I then press Stop in the browser, the threads still remain, and I have to kill them. Whereas if I kill the threads with extreme prejudice, the browser suddenly times out. I'd expected the threads to just halt when I press ctrl-C and the browser to time out immediately. But I haven't used a multithreaded framework for a while so I'm not sure this is possible. Still, the main thread can tell the others to hurry up and exit, no? I tried to see if the same thing happens with MySQL, but the search finishes so quickly (2 seconds) that I don't have time finish entering the commands. Sadly, this exercise didn't help. TG with SQLite is still hanging... -- Mike Orr <[EMAIL PROTECTED]> ([EMAIL PROTECTED] address is semi-reliable) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
