Re: [WWdevel] SetMaker is slow!

[Michael G. <ga...@ma...>]

Caching can't hurt, but I'd also take another look at the pg  
processing engine --it's pretty old code by now
That's actually a caching problem as well -- but at the moment we're  
only caching a fraction of the
code so perl has to recompile about about half the pg code each time.

Take care,

Mike


On Jul 28, 2006, at 12:16 AM, Sam Hathaway wrote:

> I was thinking that a solution to this would be to cache the entire
> output of the problem processor. For non-interactive situations like
> SetMaker, the only thing we'd need to cache on is the problem seed --
> other data (like num_correct, num_incorrect, etc.) are always the  
> same.