How to speed up massive data analysis by eliminating disk seeks
petewarden.typepad.com
How to speed up massive data analysis by eliminating disk seeks
1–10 of 28 posts
Re: How to speed up massive data analysis by eliminating disk seeks
#2I'm expecting an education on what I'm missing from the HN community!
Re: How to speed up massive data analysis by eliminating disk seeks
#3I'm certain I'm re-inventing the wheel with this approach, but I obviously haven't been researching in the right places, since I hadn't run across this approach before I cobbled it together. I'm expecting an education on what I'm missing from the HN community!
Obviously, many sites had lots of data (often a lot stored on tape) and limited main memory (especially back in the days in which it was core).
You might start here: http://en.wikipedia.org/wiki/Mainframe_sort_merge ("It is very frequently used; often the most commonly used application program in a mainframe shop.")
Show the old dogs that new dogs can learn old tricks ^_^.
Re: How to speed up massive data analysis by eliminating disk seeks
#4I'm certain I'm re-inventing the wheel with this approach, but I obviously haven't been researching in the right places, since I hadn't run across this approach before I cobbled it together. I'm expecting an education on what I'm missing from the HN community!
Re: How to speed up massive data analysis by eliminating disk seeks
#5I'm certain I'm re-inventing the wheel with this approach, but I obviously haven't been researching in the right places, since I hadn't run across this approach before I cobbled it together. I'm expecting an education on what I'm missing from the HN community!
Re: How to speed up massive data analysis by eliminating disk seeks
#6Re: How to speed up massive data analysis by eliminating disk seeks
#7This is basically a map reduce. You should look at hadoop as you start doing more complicated stuff.
Re: How to speed up massive data analysis by eliminating disk seeks
#8Re: How to speed up massive data analysis by eliminating disk seeks
#9This is basically a map reduce. You should look at hadoop as you start doing more complicated stuff.