It's highly advisable to remain on the newer code - the olde code will
eventually be deprecated, eventually unsupported, and then completely
turned off (we haven't decided on timelines for this but Q4 seems
reasonable, it'll have been a year since we initially released the newer
version).

XML is a little more expensive than straight calls, we're also attempting
to improve performance on our end as well.

Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]

On Sat, 7 Apr 2001, Fleeced wrote:

>
> Eric P ([EMAIL PROTECTED]) wrote:
> > I just went through this as well. Here are my modified files. No
> > guarantees, but they are working on my systems right now.
>
> Hey thanks for that... seems to work.
>
> The processes were using a whopping 13M each before.  Now they're down to 7.
> Still not much of an improvement in speed though.  I finally did some tests
> with various settings:
>
> It's still taking 8 seconds for my page to respond with results of a lookup.
> Playing with mod_perl, I can get that down to 6.5... not too great - and I'm
> sure its costing sales.
>
> I tested the old code (not sure version, but before all the XML stuff) gets
> response in less than 3 seconds.  This is what I consider to be a more
> reasonable response time.  I don't mind saying that I'm not too happy with
> the results... I spent alot of time with the new code, and then more trying
> to speed it up.  Its damn annoying that I can bust by gut trying to save 1.5
> seconds, when I can get a 5 second improvement just by switching back to the
> old code.
>
> Is there any way to improve performace more?  Is there any reason I
> shouldn't switch back to the old code?  I upgraded because I figured I'd be
> in a better position to be ".biz and .info ready" with a newer version of
> code - plus wanted to sell tv, etc... but I'm not sure it was worth all the
> effort.
>
> Perhaps the problem isn't even client side... I notice the newer code does
> lookups and stuff on a different port... maybe the speed difference is
> something to do with that.
>
> Fleeced
>
>
>
>
>
>

Reply via email to