Open filipecosta90 opened 4 years ago
@filipecosta90 thanks for reporting this. This is indeed a problem, could you send a PR to patch it?
Sure :)
On Sat, Dec 28, 2019, 11:27 Gabor Szarnyas notifications@github.com wrote:
@filipecosta90 https://github.com/filipecosta90 thanks for reporting this. This is indeed a problem, could you send a PR to patch it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ldbc/ldbc_snb_driver/issues/114?email_source=notifications&email_token=ABMP3VIQNIM32ZTJ2HA5H5LQ24ZYPA5CNFSM4J77Q3D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYHYTI#issuecomment-569408589, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMP3VLXAKXJUUKEGYLWMK3Q24ZYPANCNFSM4J77Q3DQ .
issue details
setting the ldbc.snb.interactive.short_read_dissipation to 0, in order to enforce only short read queries causes a constant spin on LdbcShortQueryFactory.create, forcing the following clause to be always false( we're using an the exclusive upper bound of 1 ) :
causing the following stack trace to be what's topping up the CPU:
we should test for fuzzy equality in order to fix this bug. What do you guys think?
used properties