Jan, Thanks for the reply. I need more clarification on a few things. > You can run the over + you can add more code you compile in later etc. It's > quite capable once you get under the hood, but I will not brag about their > API, doc or samples - that has "room for improvements" :D
I still need to know if the compiled scripts are per instance or compile once and use on all instances. The later would be the best of course. > I create an array of context which I re-use. Once a call arrive I need to > grab a context for CCXML and one for VXML - they do some initial processing > and then just sleep - waiting for something to happen. What I found most > effective was to use a thread pool - rather than a thread per session - the > reason is that threads are a resource budged on any computer - Also I use > processes - in a array 10 x processes and 10 x threads etc. The use of > processes makes it easier for the OS to utilize several cores - you get more > out of V8 that way. We use thread pools and context pools now (with spidermonkey). Each request that comes in over the socket is assigned a suspended thread out of the pool that is them resumed to process the request. If the request has the proper cookie then its also granted access to the "session global" if a session has been started on a previous request. I like your idea of adding another process too for better core utilization. That is something WIN32 at least appears to lack. Another question. What do you do with the instance after you are done with it. I'm assuming I'll need a pool them and also need a way of suspending them or maybe giving each thread on instance and suspending the thread. I know the devil is in the details...so please don't spare them. Thanks -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
