Sorry for the double post. Secondly have thought of using a FileReader object instead of a StringBuilder?
On Jul 12, 1:11 am, ankit m a cool dude with hot atitude <jainismru...@gmail.com> wrote: > Exactly, managing memory these days is not that important. But the solution > I am building works on a lot of string manipulations that can not be done > using string builder. Sometimes I got upto 500MB of ASCII files to process > and result produces around 850MB of output text file. When we run this > solution to P4 processors with 1-2GB RAM, it slows down the processing and > sometimes it takes 20sec to generate the output. > > But thanks a lot all for kind co-operation. > > Regards, > Akki -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to dotnetdevelopment@googlegroups.com To unsubscribe from this group, send email to dotnetdevelopment+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
