[4.x]: GQL Token Update is Expensive

[markhuot]

What happened?

Description

We're running GQL under load and AWS RDS is complaining that we're spending a lot of time waiting because we're getting so many concurrent requests all trying to update the GQL Token's lastUsed value.

Steps to reproduce

1. Send ~500 concurrent requests at a GQL endpoint
2. Notice most of the time waiting for responses to return is spent waiting for MySQL to run the lastUsed UPDATE.

Expected behavior

If this is purely for tracking purposes it'd be great if there was a way to disable this update.

Actual behavior

There is no way to skip the update on every GQL request causing bottlenecking

Craft CMS version

4.9.5

PHP version

8.3

Operating system and version

Ubuntu

Database type and version

MySQL 8.0.27

Image driver and version

n/a

Installed plugins and versions

None relating to GQL

[brandonkelly]

Just resolved this for Craft 4.11 and 5.3. Now the timestamp will only be updated if it hasn’t been updated in the past minute, which should cut down on the updated, at least once the first request has had a chance to finish updating the timestamp.