I don't know why, but I have seen these performance issues before.
It could be the string processing (it's slow in .NET 1.x). The good news is
that .NET 2.0 has a huge performance improvement in J#. Download the Visual
Studio 2005 Express beta and give it a try. It's very stable.
http://lab.msdn.microsoft.com/express/vjsharp/default.aspx
Regards,
Lars-Inge T?nnessen
Well, I'll be happy to use 2005 when it comes out in 6 months, but this is
not going to solve my problem for now, because I can't ship Beta code to my
customers. Also, it seems to me like this is a J#-specific problem, not a
.Net one, because J# Sql is 20x slower than if you use the .Net Sql classes.
So, is there any way to ship a performant J# database-driven application
before 2005 ships using J# sql classes? Or do I have to write J# sql - to -
.Net sql wrappers (quite a lot of development work, and testing) so that I
can ship my app? My users are not going to stand for a 10x reduction in
database performance.
"Lars-Inge Tønnessen [VJ# MVP]" wrote:
> I don't know why, but I have seen these performance issues before.
>
[quoted text clipped - 6 lines]
> Regards,
> Lars-Inge Tønnessen