×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 9/19/2013 8:21 AM, RPGLIST wrote:
I'm facing the need to process a very large amount of data, which is more
than likely going to come in as a SOAP or XML stream but I need to process
this quickly and without losing time with the disk arms if at all
possible.
With all of the networking going on here, all of the SOAP processing,
XML parsing, etc, you're worried about the speed of the hard drive? I
would not be.
You should start by writing your program in the most "correct", easy to
understand, easy to maintain manner. And then, look for performance
problems in actual usage. If you do have a problem, measure what's
taking the time,and determine from that how to optimize it.
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason — including
blind stupidity." -- W.A. Wulf
"We should forget about small efficiencies, say about 97% of the time:
premature optimization is the root of all evil." -- Donald Knuth
"Bottlenecks occur in surprising places, so don't try to second guess
and put in a speed hack until you have proven that's where the
bottleneck is." -- Rob Pike
The First Rule of Program Optimization: Don't do it. The Second Rule of
Program Optimization (for experts only!): Don't do it yet." -- Michael
A. Jackson
midrange.com
