# Pull request of the runtime repository and request for increasing the running time limit

**URL:** <https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919>\
**Category:** Differential Privacy Temporal Map Challenge\
**Created:** [February 12, 2021, 7:46pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919 "2021-02-12T19:46:22Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![hecci](https://avatars.discourse-cdn.com/v4/letter/h/7c8e57/32.png) [@hecci](https://community.drivendata.org/u/hecci)\
**Post date:** [February 12, 2021, 7:46pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/1 "2021-02-12T19:46:22Z")

</div>

I‘ve opened a pull request on the [runtime repository](https://github.com/drivendataorg/deid2-runtime/pull/30). I want to test my code on the server. Could someone merge it? In addition, is it possible to increase the running time limit of a single epsilon to 1 hour? Thanks.

---

<div class="post-metadata">

**Author:** ![rbgb](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@rbgb](https://community.drivendata.org/u/rbgb)\
**Post date:** [February 13, 2021, 12:49am UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/2 "2021-02-13T00:49:01Z")

</div>

Hi @hecci,  
We’ve merged the PR and updated the competition container. You should be able to run code that imports `cupy` now. We also increased the running time to 1 hour as requested. Good luck!  
Robert

---

<div class="post-metadata">

**Author:** ![hecci](https://avatars.discourse-cdn.com/v4/letter/h/7c8e57/32.png) [@hecci](https://community.drivendata.org/u/hecci)\
**Post date:** [February 15, 2021, 7:03pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/4 "2021-02-15T19:03:35Z")

</div>

Hi, it seems that 1 hour is not enough. Could you increase the running time limit to 3 hours? Thanks.

---

<div class="post-metadata">

**Author:** ![hecci](https://avatars.discourse-cdn.com/v4/letter/h/7c8e57/32.png) [@hecci](https://community.drivendata.org/u/hecci)\
**Post date:** [February 15, 2021, 10:31pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/5 "2021-02-15T22:31:02Z")

</div>

Thanks for merging the PR. I noticed the total running time for 3 epsilons is increased to 1 hours, but my code requires up to 1 hour per epsilon. Is there any chance that the total running time can be increased to 3 hours? Thank you.

---

<div class="post-metadata">

**Author:** ![glipstein](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/glipstein/32/920_2.png) [@glipstein](https://community.drivendata.org/u/glipstein)\
**Post date:** [February 16, 2021, 6:41pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/6 "2021-02-16T18:41:50Z")

</div>

@hecci - Sure thing, the runtime limit has been increased to 3h total. Good luck.

---

<div class="post-metadata">

**Author:** ![rmckenna](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@rmckenna](https://community.drivendata.org/u/rmckenna)\
**Post date:** [May 5, 2021, 12:42pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/7 "2021-05-05T12:42:08Z")

</div>

Will there be a time limit on final submissions? Or only submissions to the prescreened leaderboard?

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [May 5, 2021, 2:16pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/8 "2021-05-05T14:16:35Z")

</div>

@rmckenna As long as the final submissions will finish in a reasonable amount of time (like 4-6 hours max) then you don’t have to worry about it. You can assume the input files for final scoring will be the same order of magnitude in size.

---

<div class="post-metadata">

**Author:** ![rmckenna](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@rmckenna](https://community.drivendata.org/u/rmckenna)\
**Post date:** [May 5, 2021, 3:03pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/9 "2021-05-05T15:03:17Z")

</div>

What are the specs of the machine it will be run on? What if it takes more like 24 hours? Will such submissions be rejected?

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [May 5, 2021, 4:08pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/10 "2021-05-05T16:08:18Z")

</div>

You can assume an AWS [p2.8xlarge](https://aws.amazon.com/ec2/instance-types/) or comparable host.

Offhand 24 hours seems excessive – is that necessary for your method?

---

<div class="post-metadata">

**Author:** ![rmckenna](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@rmckenna](https://community.drivendata.org/u/rmckenna)\
**Post date:** [May 5, 2021, 4:50pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/11 "2021-05-05T16:50:45Z")

</div>

Yeah some of the methods I am considering require that much time (per epsilon). For that host would we be able to utilize all cores or will you be running other in parallel on those resources?

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [May 7, 2021, 3:43pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/12 "2021-05-07T15:43:47Z")

</div>

@rmckenna We’ve conferred with the organizers, and the maximum time per epsilon in final scoring will be 4 hours (so 8 hours total).

> For that host would we be able to utilize all cores or will you be running other in parallel on those resources?

You can use all cores.

---

<div class="post-metadata">

**Author:** ![rmckenna](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@rmckenna](https://community.drivendata.org/u/rmckenna)\
**Post date:** [May 7, 2021, 4:49pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/13 "2021-05-07T16:49:21Z")

</div>

Thank you for the clarification. Can we utilize the 8 hours total in different ways than an even split? E.g., we may want to use 6 hours for Epsilon=10.0 and 2 hours for epsilon=1.0. Would that be acceptable?

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [May 7, 2021, 7:39pm UTC](https://community.drivendata.org/t/pull-request-of-the-runtime-repository-and-request-for-increasing-the-running-time-limit/5919/14 "2021-05-07T19:39:21Z")

</div>

@rmckenna Sure, that will be fine.
