Re: using scheme for large time-series datasets?



Jason <jason.lillywhite@xxxxxxxxx> writes:

Have you tried running your stuff and seeing if things are too slow?

I have not. But you talked me into it! My colleagues tell me FORTRAN
might be the best when getting into the numerical analysis and number
crunching on large datasets. Looks like I need to do some more
investigation into Lisp because it is becoming very enjoyable (I
didn't think it was possible coming from Ruby). Thanks for the
pointers. I'm going to study the tail recursion!

What was a large data set a few years ago is not a large data set anymore.

It was large when you couldn't keep it in RAM, you had to use swap or
I/O, and when processing it meant the computer was busy for at least a
whole night, if not weeks.

But thanks to Moore law, suddenly computers are 10,000 times faster
with 10,000 times greater RAM sizes, so what was a large data set is
not anymore, and holds only a small fraction of the RAM, and can be
processed interactively even by the worse algorithms.

And we've reached the point where it's even hard to come with "large
datasets", unless you have video data, and even that, soon won't be
large anymore.

Even the human genome is less than 4GB...

--
__Pascal Bourguignon__
.



Relevant Pages

  • Re: Large RAM sizes in embedded systems
    ... with relatively large amounts of directly-addressable RAM. ... on a nominally 740GB data set. ... OS support for such large RAM sizes also appears to ... Wescott Design Services ...
    (comp.arch.embedded)
  • Re: Large RAM sizes in embedded systems
    ... embedded solution to a where a network cluster would be more ... with relatively large amounts of directly-addressable RAM. ... on a nominally 740GB data set. ...
    (comp.arch.embedded)
  • Re: Faster Marshaling?
    ... and 2 seconds to load a 9MB sized Marshal ... there's a way around this without extensive modification to ruby. ... loaded into RAM. ... entire data set in RAM all at once, because any one final data table ...
    (comp.lang.ruby)
  • Re: What GROUP BY is not...
    ... And it will only be an efficient choice if you're using a database ... quarte of the time it took to doa GROUP BY to produce the same data set. ... Starting from the moment I had entered the field into the query grid until ... button first' would be factors of ten times faster for getting a trainee to ...
    (microsoft.public.access.queries)
  • Re: Large RAM sizes in embedded systems
    ... with relatively large amounts of directly-addressable RAM. ... on a nominally 740GB data set. ... OS support for such large RAM sizes also appears to ... It may even be an effective way to prototype a system that you can come back to later and replace all the SBC's with something that's been stripped down to the bare essentials necessary to boot up and host your gargantuan blocks of memory. ...
    (comp.arch.embedded)