-
Notifications
You must be signed in to change notification settings - Fork 6
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
Performance after Adding Headless Modus #316
Comments
@drfho Maybe we should create the fallback ...I will check this ASAP. Meanwhile you can revert the both destructive calls in |
zmsbot
pushed a commit
that referenced
this issue
Oct 3, 2024
drfho
added a commit
that referenced
this issue
Oct 3, 2024
This was referenced Oct 4, 2024
Closed
Fixed by #322 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ref: 0e13c11
Exactly this change-set massivly reduces the performance of attribute listings like in the "Meta-Attribute":
/content/metaobj_manager/manage_metas?lang=ger
The creation of the table usually tales 0.2s, now it takes a least 12s
The latency is due to the modification in _cachemanager.py
0e13c11#diff-93d213afd35022330e5586bb4981eca832e4420321cdcd98646286dc2dd11c86
If this change is revoked, the performance gets to expected speed, about.
Actualy when iterating the metadict there will be an intense ping-pong of fetchReqBuff() and storeReqBuff() which costs a lot of time. Now, because self=content the request will be alsways created new by standard.create_headless_http_request(). In fact, this is not needed here at all.
So we need a solution to avoid any redundant creation of the REQUEST-Object, that is just needed for headless requests and not ordinary usage of ZMS. Maybe as global var the is just created once on startup?
The text was updated successfully, but these errors were encountered: