Skip to content
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

Trace: provide info about number of GEN_ID() calls, separately for each generator [CORE6178] #6424

Open
firebird-automations opened this issue Oct 31, 2019 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

Attachments:
trace-stat-for-number-of-gen_id-calls.png

It will be useful to show new kind of information in the trace log: number (frequency) of GEN_ID() calls which could lead to low-level contention for generators page under heavy concurrent workload.
Currently one may to see such contention in the output of fb_lock_print by analyzing data related to pending requests count.
But even when we found it, the name of problematic sequence remain unknown. The real problem is that *single* generator page contains data of hundred sequences. So, if one application decide to intensively change some "dedicated" sequence then all other connections will get influence of this activity.
Display of runtime statistics after each statement and PSQL block (proc, func, trigger) will be useful for searching of bottle-neck places in application design. This new block of statistics can be shown in form from attached picture.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

Attachment: trace-stat-for-number-of-gen_id-calls.png [ 13395 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants