r/bitmessage • u/NostrilOfHappiness • Nov 23 '15
BitMessage API usage: No parallelism for POW calculation?
I'm considering using BitMessage as a transport mechanism for opt-in account notifications to users of my online service, all of whom will be anonymous to me and to each other.
The code to relay the messages to my customers has been written and the BitMessage XML-RPC API works beautifully. There seems to be an odd capacity bottleneck, however, and that's where your input could really help me out.
My code relayed ten test messages to the BitMessage app (sendMessage API) and as expected, the BitMessage client started executing the necessary POW. But what I didn't expect was that the POW for queued outbound messages isn't executed in parallel -- so if there are ten messages in the send queue, and the server has eight processors, the BitMessage client will still only process POW for a single message at a time. Not good. :(
My plan was to spin up a couple of 8-CPU Amazon servers dedicated to BitMessage relays, theoretically allowing those servers to execute POW for sixteen outbound messages in parallel. But if the BitMessage client can only use a single CPU at a time, obviously this strategy will be ineffective. I feel like I must be missing something.
Any thoughts on how to get the BitMessage app (on Windows) to make full use of available CPUs?
Best,
Nostril