My current method can hold about 3000 threads until memory collapses. I'm looking to replace this method with something more efficient in terms of RAM usage. Something like a buffer, where each item needs far less RAM than the kind of threads I'm creating now. Then when it gets full I will use Amazon's queue as a failover mechanism.Any ideas? :-)
On Sat, Jan 26, 2013 at 12:25 AM, Hassan Schroeder < [email protected]> wrote: > On Fri, Jan 25, 2013 at 8:16 PM, Brian Braun <[email protected]> wrote: > > OK, Amazon's solution would be too expensive to use as a first option. I > > would like to use it but just after a first queue is full. This first > queue > > would be something running in my own host, using RAM to host the buffer. > > Any ideas on how to create this? > > Since you already have an implicit interface -- > > "...doing a "(new Thread(new certain Object)).start();" > > write some tests describing the behavior of that class as a resource > (in this case memory) threshold approaches. The actual design will > probably be pretty apparent. Or at least you'll have a good start. > > /* been there, done that, drunk the TDD koolaid :-) */ > -- > Hassan Schroeder ------------------------ [email protected] > http://about.me/hassanschroeder > twitter: @hassan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
