[EMAIL PROTECTED] wrote:
On Aug 30, 2006, at 10:32 AM, Nathan Folkman wrote:
So the easy way to do this would be to exec from the nsproxy. Better
option might be to wrap the C API, although I'm not entirely sure
whether or not Imagemagick is truly thread-safe. Even if it is not,
you'd probably still see better performance using the wrapped C API
from the nsproxy.
Is this concern something new for 4.5? Because OpenACS has been
exec'ing Imagemagik, sqlplus and plsql for years now with no apparent
problems. Have we just been really lucky?
janine
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
If it ain't broke don't fix it. ;-) But if you're running into memory
issues, the nsproxy approach I mentioned can help. Another nice thing in
general about running code from within the nsproxy is that you can
easily kill of the nsproxy processes which can help you reclaim memory
that otherwise might be tied up in the Tcl threaded allocator shared
pools. This is more of a general side affect, and not really relevant to
the exec'ing discussion...
- n
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
