I am making a solution where I need to loop through 300.000 loans in one
batch-run and do some calculations on each loan. I would like the
calculations to be in Excel-services, but I have troubles with the
performance and stability.
For testing purposes I made a simple example where I made a loop running
300.000 times and called an Excel Sheet thorugh Excel services at every loop.
The Excel Sheet had one input and one output. (The output was the input +
1000). When I startes the loop proces I got a message after 2 minutes, saying
that the server was not responding. If I started the proces again, there
would go 2 minutes again before the server stopped responding
The Sharepoint-server is 3,6 GHz with 2 GB ram. It is not overloaded when
the proces is running, so I am having difficulties understanding why it stops
responding...
All right.. I am a newbee with webvservices, so I hope you can help me to
understand whats wrong.
- Is 300.000 calls to a webservice to much?
- Is there something I can do to optimize the calls to ExcelServices?
- Is there a way not to smplement ExcelServices as a web service and instead
call a local Excel-installation on the server (To boost performance)?
Hope somebody can help me...
Excel services has limits on the number of "sessions" that can be opened,
depending on your web service code, you could be not closing the sessions,
this would cause timeouts. Thing is, opening and closing them is not a
great idea either, especially in the 300K range! Ideally, you might try
only keeping open one session and reseting the data for each loan and then
processing.
Still, Excel services isn't the fastest architectural decision you could
have made here. Not sure what your "inputs" are, but a custom .NET
multi-threaded application to do your processing would be a lot faster!
Chris
"Mads Nielsen" <Resultm...@newsgroups.nospam> wrote in message
news:66532402-7F1E-4E18...@microsoft.com...