SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : All About Sun Microsystems
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Michael L. Voorhees who wrote (10495)7/17/1998 1:13:00 PM
From: Robert  Read Replies (1) of 64865
 
Jini is not the technology that you need.

The main problem you will have will be the size of your matrices, which I assume to be large enough that copying them around would not be a sensible thing to be doing. This means that the threads of execution should all have access to the same memory. To the best of my knowledge, Jini copies all of the objects instance variables and sends them across the network to the object pools for service, not something to be done with large matrices. However, locally within a thread, its instance variables can be shared with subthreads, so rewriting your problem as a threaded application under Java is certainly feasible, but then you will have to deal with asynchronous coordination of the threads. You are probably better sticking with MPI and letting it solve these problems for you, which it was designed to do.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News