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
Hey @bensheldon - just found this, nice that you forked it and maintain!
So, I'm curious why Que performs so much better than QC on - I thought, based on this release it was comparable or slightly better, but the docs here suggest otherwise: but, my comment was on a laptop - these benchmarks on big machine. Could that be it? If you have any thoughts, great.
Only I think I noticed inside the benchmarks themselves was that Que seems to enqueue, and destroy in the same transaction; I'd assume this results in zero writes to tables or indexes; however QueueClassic has a comment about not knowing how to delete it - i.e. it's actually going to be writing it to disk. I'm curious how much difference that would make, and will make a PR.
The text was updated successfully, but these errors were encountered:
Hey @bensheldon - just found this, nice that you forked it and maintain!
So, I'm curious why Que performs so much better than QC on - I thought, based on this release it was comparable or slightly better, but the docs here suggest otherwise: but, my comment was on a laptop - these benchmarks on big machine. Could that be it? If you have any thoughts, great.
Only I think I noticed inside the benchmarks themselves was that Que seems to enqueue, and destroy in the same transaction; I'd assume this results in zero writes to tables or indexes; however QueueClassic has a comment about not knowing how to delete it - i.e. it's actually going to be writing it to disk. I'm curious how much difference that would make, and will make a PR.
The text was updated successfully, but these errors were encountered: