Reducing jatos.appendResultData in OSWeb Study
I am running an OSWeb experiment online through the JATOS server right now that has been made public to host experiments during the pandemic and am having some data storage issues. They are saying my experiment collects about 10 jatos.appendResultData per second that leads to an entire database update each time, which are all being logged and bogging down the available storage of the server. How would I go about reducing the amount of jatos.appendResultData my study sends within the OS framework? Could this result from having more than one logger object in the experimental flow? I'm not really sure where this backend parameter sources from, so any suggestions would be greatly appreciated. Thanks!