Too much db writing because of searchlog table

[Wayne Luke]

Why are you using MyISAM and not INNODB?

[moonshiner]

It is crazy that an issue that old causes still so much trouble!

I am currently debugging an error that causes Queries take longer than 20 seconds. The query UPDATE searchlog SET `dateline`=1465943922 WHERE (`userid` = 3) is somehow running always in an full table lock.

[szantog]

The searchlog table is totally useless with this structure, but generate tons of db writing. Only can match within 60 sec with the same user, with the same search JSON. I'm talking about core/vb/api/search.php getSearchResult(). Btw we disabled the search completely, We only have a Latest Topics block on every pages.

Why is necessary to write record for every different user, although the results are the same for a user group? Or/and why isn't it on a real cache layer so eg. memcache can be used to store it?

How can we disable or decrease to write into this table unless vb hack, or redesign our pages?