On 3/24/06, Mr. Shawn H. Corey <[EMAIL PROTECTED]> wrote: > Brian McKee wrote: > > au contraire - If he is using the Spreadsheet::WriteExcel I'm sure it > > buries his server - > > it hits mine hard with just one user. > > > > I don't have a solution, just a comment that it's a real problem. > > I don't suppose you could pre-generate some of the requests? > > like during off-hours or something? > > > > Brian > > Oops, that dratted reply bug has hit again! > > > \ / > o > -( )- > -( )- > -( )- > (_) > > > I don't use Spreadsheet::WriteExcel but if it's so slow here's an idea. > If the output involves only data, that is, no formulas or macros, then > you could output it in Comma-Separated-Values format (CSV) and load it > into your spreadsheet that way. There are a number of modules on CPAN > <http://cpan.org/> that can do this. > > But then again, I still would do a test on the server just to make sure > it is not the cause of the problem. >
If it's just tabular data, you could use Win32::OLE, too. It's usally faster than Spreadsheet::WriteExcel because it uses the native apps and system calls to so the work instead of parsing the binary file itself. It's only an option on Windows, though. If you're creating these files on a unix platform, you're out of luck. No matter which platform, though, if tabbed files are a possibility at all, use them. Recent versions of Excel will also import some XML schemas. If generating usable output quickly is your goal, go for the text output. Excel will import even large text files quickly when the user opens them, but using modules to export even small data sets to excel format is tedious. HTH, --jay -- -------------------------------------------------- This email and attachment(s): [ ] blogable; [ x ] ask first; [ ] private and confidential daggerquill [at] gmail [dot] com http://www.tuaw.com http://www.dpguru.com http://www.engatiki.org values of β will give rise to dom!
