On Mon, Nov 26, 2012 at 08:25:47PM +0100, Alessandro Molina wrote: > Just keep in mind that asyncjob is meant for short term tasks and on > production you will probably start more that one process of your > application. > Starting more than one process will result in having multiple execution > queues (one for each process) which greatly reduces the side effects of > having the GIL in place. Just to calrify that, are you suggesting something like. $ python myjob.py & $ python myotherjob.py &
ie two different python interpreters for different functions? I've got a lot of back-end work going on and while most (all?) is asynchronous calls (with the associated extra madness that entails) I'm stil worried about processing times, mainly around the database access speeds though of course I'm testing on sqlite so that might be the problem. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- 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?hl=en.
