Willing to pay to solve a Visual Studio debug mode performance problem

View: New views
2 Messages — Rating Filter:   Alert me  

Willing to pay to solve a Visual Studio debug mode performance problem

by Pedram Abrari :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Dear IKVM developers

 

We have been to trying to overcome a problem with IKVM for the past couple of months and have been unsuccessful.  We’re looking for IKVM developers who can help us diagnose/resolve/workaround the problem.  If you’re interesting in this offer please email or call me.

 

Here’s the problem:

 

We have an IKVM application which is in large part pre-compiled using ikvmc but dynamically compiles some jars. When this application is referenced as a set of dlls in a Visual Studio C# application, if the application is run from VS without debugging then everything performs well. But if the application is run in debug mode from Visual Studio then it can take a half hour to load up and requires a humongous amount of memory which at times causes the app to run out of memory.  Our experimentation indicates that this problem with VS debug mode gets exponentially worse the more dynamically complied jars there are.  With one dynamically compiled jar things are slow but reasonable.  With two the performance degrades by 4x.  With three the performance degrade by 10x.

 

Does this sound like a problem you’ve run into or are willing to help solve?

 

Best Regards

 

Pedram Abrari

CTO & Co-founder

Corticon Technologies, Inc.

888-619-2424 Toll Free

650-787-2838 Mobile

650-212-2424 x215 Office

pedram@...

 


------------------------------------------------------------------------------

_______________________________________________
Ikvm-developers mailing list
Ikvm-developers@...
https://lists.sourceforge.net/lists/listinfo/ikvm-developers

Re: Willing to pay to solve a Visual Studio debug mode performance problem

by Jeroen Frijters :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Pedram,

I did some investigating. I tested running Eclipse with a debugger attached again,which I've done previously and didn't work back then, it still doesn't work and results in the same things you see (i.e. huge memory consumption and crashes).

Other testing revealed that there is a bug in the .NET Framework symbol generation for dynamic types that can result in access violations and that simply enabling symbol generation results in a big slowdown, so I disabled symbol generation and tried running Eclipse under the debugger again, unfortunately this still resulted in massive memory consumption and I aborted the process after it had consumed 1.5 GB and 35 minutes and still wasn't anywhere near started up (without the debugger it takes about 1.5 minutes to start Eclipse).

In summary, I don't think you'll have much luck tackling this from the IKVM end, you might want to try opening a support case with Microsoft.

BTW, I will be adding an app.config switch to ikvm to enable/disable symbol generation for dynamic code.

Regards,
Jeroen

> -----Original Message-----
> From: Pedram Abrari [mailto:pedram@...]
> Sent: Friday, July 24, 2009 23:48
> To: ikvm-developers@...
> Subject: [Ikvm-developers] Willing to pay to solve a Visual Studio
> debug mode performance problem
>
> Dear IKVM developers
>
>
>
> We have been to trying to overcome a problem with IKVM for the past
> couple of months and have been unsuccessful.  We're looking for IKVM
> developers who can help us diagnose/resolve/workaround the problem.  If
> you're interesting in this offer please email or call me.
>
>
>
> Here's the problem:
>
>
>
> We have an IKVM application which is in large part pre-compiled using
> ikvmc but dynamically compiles some jars. When this application is
> referenced as a set of dlls in a Visual Studio C# application, if the
> application is run from VS without debugging then everything performs
> well. But if the application is run in debug mode from Visual Studio
> then it can take a half hour to load up and requires a humongous amount
> of memory which at times causes the app to run out of memory.  Our
> experimentation indicates that this problem with VS debug mode gets
> exponentially worse the more dynamically complied jars there are.  With
> one dynamically compiled jar things are slow but reasonable.  With two
> the performance degrades by 4x.  With three the performance degrade by
> 10x.
>
>
>
> Does this sound like a problem you've run into or are willing to help
> solve?
>
>
>
> Best Regards
>
>
>
> Pedram Abrari
>
> CTO & Co-founder
>
> Corticon Technologies, Inc.
>
> 888-619-2424 Toll Free
>
> 650-787-2838 Mobile
>
> 650-212-2424 x215 Office
>
> pedram@... <mailto:pedram@...>
>
>


------------------------------------------------------------------------------
_______________________________________________
Ikvm-developers mailing list
Ikvm-developers@...
https://lists.sourceforge.net/lists/listinfo/ikvm-developers