Re: opcode caching / speed-up app

Sounds to me like the major issue is probably the XML parsing. Depending on what you're doing, you may want to switch to a relational database. Alternately, you can just add more servers and distribute the load.

Is this a secret or can you link us to the actual app so we can get a better idea of where the hang-up may be and how you can improve things?

Comment on Re: opcode caching / speed-up app

Replies are listed 'Best First'.
Re^2: opcode caching / speed-up app by Anonymous Monk on Sep 16, 2013 at 16:51 UTC
Sorry, I won't be able to provide a link to it. I appreciate the advice. I'll look into more into profiling but I'm sure some sort of implementation of something like FastCGI will be needed as a point. Would you happen to have a good (simplified) link on how to use FastCGI? The apps are tested and used on Windows and later installed on both Windows and Linux. Thanks again.	[reply]
Re^3: opcode caching / speed-up app by TJPride (Pilgrim) on Sep 16, 2013 at 20:21 UTC
The work I do is more low-volume, high-processor utility runs, and in the instances where I have to deal with high-volume traffic, I use PHP instead (yes, this is a Perl site, but both languages have their strengths and weaknesses, imho). Someone more pure Perl will have to supply you with info on FastCGI.	[reply]