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
Hi, I have a question when i build and run DBx1000.
When i run 'rundb', CC_ALG=TIMESTAMP with TPC-C benchmark, I found the interested one.
when i change the PERC_PAYMENT value 0.5 to 0 or 0.5 to 1.0, It does work well. (it also works well in YCSB workload).
But the other case doesn't work. (the value 'PERC_PAYMENT' is not both 0.0 and 1.0)
My question is, is the error an algorithmic problem in TIMESTAMP or in other factor?
I've tried to find the error in code, but this problem is really not simple to me.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi, I have a question when i build and run DBx1000.
When i run 'rundb', CC_ALG=TIMESTAMP with TPC-C benchmark, I found the interested one.
when i change the PERC_PAYMENT value 0.5 to 0 or 0.5 to 1.0, It does work well. (it also works well in YCSB workload).
But the other case doesn't work. (the value 'PERC_PAYMENT' is not both 0.0 and 1.0)
My question is, is the error an algorithmic problem in TIMESTAMP or in other factor?
I've tried to find the error in code, but this problem is really not simple to me.
Thank you.
The text was updated successfully, but these errors were encountered: