oTree Forum >

Using app_after_this_page on a game with many apps/rounds. Slow loading time?

#1 by ch_behavioralecon

Hi all,

I am building an experiment that incorporates timeouts spanning multiple pages/rounds/apps, where I also have several apps and many many rounds (10 apps with 270 rounds each to be exact, and then a results app at the end). I am using app_after_this_page in order to send certain participants to the last app if they time out after a certain point.

However, I've noticed that when someone times out, it takes quite a long while for the last app to load. Furthermore, if I have multiple players on the same session, the slow loading time of one also slows down the loading time of the other. I'm especially worried about this second part as the timer still goes down for the second participant even if they've clicked the button for the next page.

I thought this wouldn't be an issue as, from what I understand, with app_after_this_page we skip any apps between the current app and the last one. However, the slow loading time implies to me that oTree still runs through the many apps/rounds in some way. Is this correct? Is there a more efficient way to skip apps without having to reduce the number of apps/rounds?

Many thanks in advance.

Write a reply

Set forum username