[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cgiapp] Plugins and shared memory


Wojciech Pietron wrote:
> Hi,
> 
> I apologize all cgi-app users if my question is trivial or naive. 
> 
> Is there a possibility to put all the C::A::Plugin:* modules into shared
> memory as it is in the case of HTML::Templates that uses
> IPC::SharedCache to cache templates? It could speed up all cgi scripts
> using C::A and its plugins.

Shared memory just means that perl has loaded it. In the case of
non-perl objects (templates, etc) there are usually some cache modules
that people use to put them into shared memory.

In the case of perl modules (like any of the plugins) they are in memory
by virtue of loading them. If you are running under normal CGI (mod_cgi
in apache) then it's just the same. You can't get a speed up. If you are
in a a persistant environment (mod_perl) then by 'preloading' the
modules they become shared by all processes and it's a tremendous speed
improvement.

If you are talking about some sort of in memory cache in an process
outside of perl that would hold compiled perl code until you called for
it... no such beast exists (that I'm aware of) and it would be extremely
non-trivial to do.

Does that help?

-- 
Michael Peters
Developer
Plus Three, LP


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed


Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.