You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ) :
double coinToss = random.nextUniform( min, max );
if ( state > coinToss )
{
return innerFactory.create(
personIdBuffer,
messageIdBuffer,
previousOperation,
previousOperationActualStartTimeAsMilli,
previousOperationRunDurationAsNano,
state
);
}
else
{ return null; }
causing the following stack trace to be what's topping up the CPU:
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
The text was updated successfully, but these errors were encountered: