After a few performance improvements, I did some loading time tests for #serci, between my home network (wifi) and a random VPN where the service is running.
echo \"html,redirect\" | tee timestamps.csv\r\nfor i in $(seq 1 1 100); do\r\n HTML=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de)\r\n REDI=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de?q=test)\r\n echo \"$HTML,$REDI\" | tee --append timestamps.csv\r\ndone
Across 100 runs for loading the site's HTML (generated from pure #PHP) versus a redirect to a chosen service (here the default #MetaGer), I can measure on average 0.28s for loading the frontend (HTML) and 0.13s for processing input and issuing the redirect.
I am quite happy with this relatively low overhead, although performance may decrease a little if more services are added (currently: 47). At some point maybe an #sqlite database may be more efficient than my pre-constructed #json files which are loaded on-demand.
", "mediaType":"text/html", "attachment":[], "tag":[ {"type":"Hashtag","name":"#serci","href":"https://social.jayvii.de/tags/serci"}, {"type":"Hashtag","name":"#PHP","href":"https://social.jayvii.de/tags/PHP"}, {"type":"Hashtag","name":"#MetaGer","href":"https://social.jayvii.de/tags/MetaGer"}, {"type":"Hashtag","name":"#sqlite","href":"https://social.jayvii.de/tags/sqlite"}, {"type":"Hashtag","name":"#json","href":"https://social.jayvii.de/tags/json"} ], "type":"Note", "id":"https://social.jayvii.de/objects/G_DxxoDGL2g" }