[Bug]: Accept/Decline Invitation is slow

[avinash-0007]

trafficstars

⚠️ This issue respects the following points: ⚠️

• [X] This is a bug, not a question or a configuration/webserver/proxy issue.
• [X] This issue is not already reported on Github (I've searched it).
• [X] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• [X] Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• [X] I agree to follow Nextcloud's Code of Conduct.

Bug description

i invited 45 invitees and now when one of the attendee accept , it takes more then 12seconds

And what i see in every user accept it enters 96 enteries in calendarobjects_props two enteries for each attendee, two for orgnaizer and 4 for status,location summary,description 452+12+4 =96 so i didnot understand why an accept request inserting 96 records and may be due to this face its slowing down https://github.com/nextcloud/server/blob/888ffa498d3a08bb32591704806ee90075b4bc20/apps/dav/lib/CalDAV/CalDavBackend.php#L3008-L3063

Steps to reproduce

1. Go to calendar and create event
2. invite large number of attendees 3.Now when attendee accept request it will take more then 12 seconds

Expected behavior

Accept invitation should be fast

Installation method

None

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• [ ] Default user-backend (database)
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Configuration report

No response

List of activated Apps

Enabled:
  - accessibility: 1.10.0
  - activity: 2.16.0
  - calendar: 3.4.0-alpha.1
  - cloud_federation_api: 1.7.0
  - comments: 1.14.0
  - contacts: 4.2.3
  - cookbook: 0.9.18
  - dav: 1.22.0
  - drop_account: 2.1.0
  - email-recovery: 2.1.1
  - federatedfilesharing: 1.14.0
  - files: 1.19.0
  - files_pdfviewer: 2.5.0
  - files_rightclick: 1.3.0
  - files_sharing: 1.16.2
  - files_trashbin: 1.14.0
  - files_videoplayer: 1.13.0
  - forms: 2.5.1
  - increasestoragebutton: 3.5.1
  - integration_google: 1.0.8
  - logreader: 2.9.0
  - lookup_server_connector: 1.12.0
  - news: 20.0.0
  - notes: 4.5.1
  - notifications: 2.12.1
  - oauth2: 1.12.0
  - onlyoffice: 7.5.8
  - password_policy: 1.14.0
  - photos: 1.6.0
  - privacy: 1.8.0
  - provisioning_api: 1.14.0 
  - recommendations: 1.3.0
  - serverinfo: 1.14.0
  - settings: 1.6.0
  - sharebymail: 1.14.0
  - snappymail: 2.25.2
  - text: 3.5.1
  - twofactor_backupcodes: 1.13.0
  - updatenotification: 1.14.0
  - viewer: 1.8.0
  - workflowengine: 2.6.0
  - dashboard: 7.3.0
Disabled:
  - admin_audit
  - circles: 24.0.1
  - contactsinteraction: 1.5.0  
  - encryption
  - federation: 1.14.0
  - files_external: 1.12.1
  - files_versions: 1.17.0
  - firstrunwizard: 2.10.0
  - ldap_write_support
  - nextcloud_announcements: 1.13.0
  - oidc_login: 2.3.3
  - rainloop: 7.2.5
  - support: 1.7.0
  - survey_client: 1.12.0
  - systemtags: 1.14.0
  - theming: 1.12.0
  - user_backend_sql_raw: 1.3.0
  - user_status: 1.4.0
  - weather_status: 1.4.0

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[szaimen]

Hi, which nc version?

[avinash-0007]

@szaimen > Hi, which nc version?

NC 24.0.8

[szaimen]

Hi, please update to 25.0.7 or better 26.0.2 and report back if it fixes the issue. Thank you!

My goal is to add a label like e.g. 26-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort!

If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+

[nextcloud-command]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[avinash-0007]

@szaimen Okay. will update you soon.