[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-user
Subject:    threading : "context switching" : optimal configuration
From:       James Maes <jmaes () sportingnews ! com>
Date:       2001-10-10 16:50:38
[Download RAW message or body]


another resend.


Heres another one for you all.
 
The sandbox I am building around Velocity will have to handle a sizeable load
upto ~6,500 rendering per hour.  During any given hour it will be common for
as many as 20 threads to be rendering at the same time.  Is the singleton
model of the engine suited for this via multiple threads or should I commit
a different instance of velocity for each processing thread and have a pool
of velocity's waiting.
 
Also I am aware of the thread last week about which parts of velocity are
not thread safe.  That is not an issue here since each rendering will have a
unique context inited for it.
 
Thanks again.
 
-james







-- 
 
------------------------------------
|| James Maes        
|| Senior Programmer 
|| jmaes@sportingnews.com 
|| The Sporting News     
|| www.sportingnews.com 
------------------------------------

"given enough time and resources we can accomplish anything"

[prev in list] [next in list] [prev in thread] [next in thread]