MDEV-29659 and more specifically discussions around the manual update in MDEV-33041 highlighted a possible Spider performance optimization. It would be reflected in this manual update we were considering:

Please note that not granting SUPER and setting spider_internal_sql_log_off to 0 or 1 [may/will] lead to

slowdowns as SET SQL_LOG_OFF statements will be executed for each query on the data node.

The first step would be to clarify if this is the case. If so, it can likely be optimized as in some cases these statements may not be needed (for example if it was in the correct on/off state already), or possibly grouping of statements, etc.