in reply to Re^5: Thread sharing a bit vector??
in thread Thread sharing a bit vector??

Do you need to do this once or many times?

Either way, set this going with your current solution & data NOW! Once it is running, then explore further possibilities.

If: a) you are going to do this many times in the future; b) you can tolerate a delay (>1 month) before getting a good solution: c) have sufficient C knowledge to help me port and extend my XS bit-vector code to whatever platform you are running on; then email me. (See my home node.)


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Replies are listed 'Best First'.
Re^7: Thread sharing a bit vector??
by traceyfreitas (Sexton) on Apr 13, 2012 at 11:00 UTC

    I will be running this only as often as practical. Meaning if it takes 2 weeks to produce the data I need, then it would be run every 2 months or longer. If it could produce it in, say, just a few days, then I would re-run it with updated data at least every month. The data set that this program chews on grows every month, and I foresee this program to be used for years to come.

    I work with x86_64 machines (linux) and it'll be about a week before I can get the program completely re-tooled to use Bit::Vector. I shall email you!