On 11/19/2014 11:35 AM, Ovidiu Sas wrote:
It shouldn't ... Based on how many workers and cores you have, the
probability of having collisions should be pretty low. You can
process more then the minimum of workers/cores available on your
server.
Yeah, I know. As I've remarked before, I find th
s/You can process/You can't process
Typo :)
-ovidiu
On Wed, Nov 19, 2014 at 11:35 AM, Ovidiu Sas wrote:
> It shouldn't ... Based on how many workers and cores you have, the
> probability of having collisions should be pretty low. You can
> process more then the minimum of workers/cores availab
It shouldn't ... Based on how many workers and cores you have, the
probability of having collisions should be pretty low. You can
process more then the minimum of workers/cores available on your
server.
Regards,
Ovidiu Sas
On Wed, Nov 19, 2014 at 11:21 AM, Alex Balashov
wrote:
> Thanks, it was
Thanks, it was actually increment I was interested in.
Can one get around it with an intermediate variable?
$var(y) = $shv(x);
$shv(x) = $var(y) + 1;
I would just use a lock(), but I'm afraid that it will serialise message
processing too much at high volume, due to the blocking.
On 19 Nove
For what kind of operation?
Reading or setting the value are safe, but updating it with its own
value used in an expression is not.
Safe:
xlog("value is $sht(x)\n");
$sht(x) = 1;
Race:
$sht(x) = $sht(x) + 1;
Cheers,
Daniel
On 19/11/14 00:27, Alex Balashov wrote:
> Does setting $shv()s in scr
Does setting $shv()s in script require lock()ing, or is it inherently
thread-safe?
Thanks!
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
__
