>
> When folks have an app that needs more RAM than a typical server, what is
> the first and most common steps they take?
>
First step would be to put more RAM, if you've maxed out physical RAM, you
can add swap.
I'd also look at reducing the RAM usage first. Are you sure you can't
stream t
Did you pull all 4 million at once? Are you doing a huge sorting operation
over millions of records in memory? Then yes, you are going to use a lot of
memory. There aren't many ways around it.
Eclipse Collections (and others) have smaller collections than java.util.
Maybe they make a difference
I don't know about MySQL specifics, but I did a similar job on top of
postgresql and relied on its built in temporary tables, indexes and
spill-to-disk functionality, the dataset/computation in question was
already blowing up a Ruby process. There's no need to reinvent it in
clojure if the database
I recently worked on a minor project that nevertheless needed to use 10
gigs of RAM. It ran on a reasonably powerful server, yet it taxed that
server. And I wondered, how are people scaling up such processes? If my
approach was naive, what does the less naive approach look like?
I wrote a simp
