Interchange Developer Resource
[Date Prev][Date Next][Thread Prev][Thread Next][Interchange by date ][Interchange by thread ]

[ic] Interchange using lots of cpu...



> It sounds like something somewhere is copying either the result set or
> something associated with it with some nasty quadratic behavior.  It
> wouldn't be Safe.pm would it?  Or some other consequence of firing
> up perl?  I feel that this is the most likely explanation at this point.

In fact, when using [benchmark] on nearly every line, it seems that the
problem is not related to 'firing up perl'.  A single occurrence of
	[ARTICLE-param col10]
for example can take 0.07 seconds during initial loop iterations on 'large'
result sets.  A bit surprising.  If you want to dump out the content of 10
fields like that, voila, 0.7 seconds PER ROW, gradually speeding up as
results are emitted.  The last couple of hundred rows fly by, so unless
you process more than that you won't notice the problem.

As that seemed so fundamental I gave up on that approach and just dumped
the [query] results out in a single [perl] tag -- it now runs 100x faster
at least.

Now I've got to try and convince my colleagues that interchange is not
simply a toy.  If we end up doing everything in perl anyway, why use
interchange?

- gordon


Search for: Sort by: