Re: Architecture ideas for batch processing?

Alan Meyer wrote:
> "Ray in HK" <ray@xxxxxxxxx> wrote in message news:d8ge0v$20e4@xxxxxxxxxxxxxxxxxxxxxxxxx
> > What are the market price of ram.
>
> Thanks for the reply.
>
> RAM can be surprisingly expensive when you buy it in multi-bank,
> multi-gigabyte modules for Sun machines. But your point is well
> taken. The extra cost may be justified.
>
> There may be some processing efficiencies besides using
> less memory management in a multi-threaded vs. multi-tasking
> design.
>
> Maybe someone has experience in this area?

Ask unix or windows experts. There are at least three disadvantages:

1.Allocating a process uses more resource than a new thread. But given
Java's own resource need, .... :-)

2.Context-switching processes takes longer time than switching threads.

3.On non-SMP, sync between processes are super heavy compared to
thread's. In x86 all you need to do mutex between threads is an
exchange command, but between processes....


PS: none of above is really important.

.

Relevant Pages

  • Re: Architecture ideas for batch processing?
    ... | RAM can be surprisingly expensive when you buy it in multi-bank, ... | multi-gigabyte modules for Sun machines. ... fill them up with RAM and run your batch ... idea of the what the nature of your batch processing tasks is :-). ...
    (comp.lang.java.programmer)
  • Re: Architecture ideas for batch processing?
    ... RAM can be surprisingly expensive when you buy it in multi-bank, ... multi-gigabyte modules for Sun machines. ...
    (comp.lang.java.programmer)