I want scheduled reports to be able to run faster than one per minute. Understanding that this is getting a little bit into mad science territory, has anyone ever tried running parallel instances of the Tessitura Report Server?
I figure that if I had a way to offset the polling time by a certain interval (30 seconds for two instances, 20 seconds for 3 instances, 15 seconds for 4 instances, etc) I could increase the pace of report running. I know that the instant after the report server polls, it marks the request as running (if it has a due request), so I think this would prevent two report servers from trying to run the same request, but I don't know what a report server would do if it sees a running request being handled by a _different_ report server -- if it would just pick up the next scheduled request, or if it would count that running request against the concurrency setting of 1. Further unknown is whether running two instances of the report server would be vulnerable to the email file mixup bug that is mitigated by the single-concurrency setting. No idea if EMAIL_REPORT_PATH T_DEFAULT can be overridden at the client level, but that would probably solve the problem if so.
Gods, isn't one bad enough?