New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce internal contention in background garbage collector [CORE4936] #5227
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 RC 1 [ 10584 ] |
Commented by: @hvlad When background garbage collector is active (SuperServer mode with gc_policy set to "combined" or "background") all worker In FB3 we have multy-threaded SS engine. Therefore we need to protect internal data of Garbage Collector from concurrent Latest testing (using SSD and FW=OFF) shows that notification of garbage collector by different threads could be serialized Goal of this ticket is to avoid usage of exclusive syncs in hot points as much as possible. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested Test Details: Issues of this ticket were confirmed by benchmark that was done using OLTP-EMUL test in sep-2015. For SuperServer following results were obtained: FW = OFF: usual build = 6806 FW = ON: usual build = 5181 So, effect is visible when FW = OFF (SATA storage was used used in all tests). firebird.conf: AuthClient = Legacy_Auth,Srp,Win_Sspi Detailed reports one may see inattached .7z |
Modified by: @pavel-zotovAttachment: benchmark-gc_combined-oltp-emul-100-attaches-for-6-hours_-_SS.7z [ 12916 ] |
Modified by: @pavel-zotovAttachment: benchmark-gc_combined-oltp-emul-100-attaches-for-90-minutes_-_Cs.7z [ 12917 ] |
Modified by: @pavel-zotovAttachment: list-staying-gc-overall-comparison.xls.7z [ 12918 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] Test Details: Issues of this ticket were confirmed by benchmark that was done using OLTP-EMUL test in sep-2015. For SuperServer following results were obtained: FW = OFF: usual build = 6806 FW = ON: usual build = 5181 So, effect is visible when FW = OFF (SATA storage was used used in all tests). firebird.conf: AuthClient = Legacy_Auth,Srp,Win_Sspi Detailed reports one may see inattached .7z => Issues of this ticket were confirmed by benchmark that was done using OLTP-EMUL test in sep-2015. For SuperServer following results were obtained: FW = OFF: usual build = 6806 FW = ON: usual build = 5181 |
Submitted by: @hvlad
Attachments:
benchmark-gc_combined-oltp-emul-100-attaches-for-6-hours_-_SS.7z
benchmark-gc_combined-oltp-emul-100-attaches-for-90-minutes_-_Cs.7z
list-staying-gc-overall-comparison.xls.7z
Commits: f7e248c FirebirdSQL/fbt-repository@886459f
====== Test Details ======
Issues of this ticket were confirmed by benchmark that was done using OLTP-EMUL test in sep-2015.
Detailed reports one may see inattached .7z files.
For SuperServer following results were obtained:
FW = OFF: usual build = 6806
FW = OFF: patched build = 8071
FW = ON: usual build = 5181
FW = ON: patched build = 5111
The text was updated successfully, but these errors were encountered: