A user on 0.18.1-rc6 on Lemmy.world reported an upvote error.
I think the API should have a counter of the error and that the API should return the count. If it isn’t saved, fine, but maybe return system uptime on errors too.
This puts the power more in the hands of clients instead of server operators to know what is gong on internally with the Lemmy servers that are falling flat on their face performance-wise in the 0.18.1 era.
Someone finally opened a ticket about Vote performance on the major servers. I just do not get why the big server operators are not opening issues and sharing server logs. What is going on inside the Rust code isn’t being understood by enough newcomers to the project.
https://github.com/LemmyNet/lemmy/issues/3395
There is a 10 second pause between each comment vote in this test to Lemmy.ml:
0 timeConnect 7.425 timeParse 0.005 errorCount 0 https://lemmy.ml/ vote 1 1 timeConnect 7.376 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 2 timeConnect 17.577 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 3 timeConnect 8.001 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 4 timeConnect 3.344 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 5 timeConnect 6.646 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 6 timeConnect 10.375 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 7 timeConnect 6.55 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 8 timeConnect 7.988 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 9 timeConnect 3.68 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 10 timeConnect 4.364 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 11 timeConnect 12.162 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 12 timeConnect 40.916 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 13 timeConnect 16.446 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 14 timeConnect 11.088 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 15 timeConnect 5.357 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 16 timeConnect 3.267 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 17 timeConnect 5.807 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 18 timeConnect 7.387 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 19 timeConnect 8.429 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 20 timeConnect 4.164 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 21 timeConnect 5.317 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 22 timeConnect 8.147 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 23 timeConnect 3.293 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 24 timeConnect 6.907 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 25 timeConnect 3.645 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 26 timeConnect 4.157 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 27 timeConnect 11.53 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 28 timeConnect 21.184 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 29 timeConnect 9.991 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 30 timeConnect 5.82 timeParse 0.001 errorCount 0 https://lemmy.ml/ vote 1 31 timeConnect 3.882 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 32 timeConnect 4.324 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 33 timeConnect 3.272 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 34 timeConnect 4.133 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 35 timeConnect 4.99 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 36 timeConnect 8.131 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1 37 timeConnect 5.391 timeParse 0 errorCount 0 https://lemmy.ml/ vote 1