You can find our new documentation site and support forum for posting questions here.
delay in call-cache hitting?
I ran a job. It was the first for call-caching so it was a designed to be a "miss". Indeed it did "miss".
Then, less than 5 min later, I asked Chet to run it to test the call-caching hitting. But when he ran it, he got a "miss".
20 minutes later I asked Gordon to run the same config but he did get a hit.
So does this indicate some delay in CC?
I tested call-caching with a separate different WDL, and got a hit (after re-submitting myself) right after a successful submission, but it was me submitting and hoping to get a "hit" using my credentials. In this case, the WDL had a two inputs (strings) and no outputs. Also, in this case, right after a submission finished I got a "hit" (success).
In contrast, with the WDL, that Chet and Gordon ran, it had numerous more inputs and it had about 20 outputs. Is there delay associated with WDL complexity? or with different users trying to use call-caching?
I wonder if anyone else has had similar experiences or observations.