Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/guides/max-execution-time.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@
"The maximum execution time for a job is the smaller of these values:\n",
"\n",
"- The value set for `max_execution_time`\n",
"- The service-determined job timeout value\n",
"- The service-enforced maximum limit (3 hours)\n",
Comment thread
JJRBEST marked this conversation as resolved.
Outdated
"\n",
"The `max_execution_time` value is based on *QPU usage*, not wall clock time.\n",
"\n",
Expand Down Expand Up @@ -70,7 +70,7 @@
"<span id=\"max-QPU\"></span>\n",
"## Service-calculated maximum execution time\n",
Comment thread
JJRBEST marked this conversation as resolved.
Outdated
"\n",
"The service calculates an appropriate job timeout value based on the input circuits and options. This service-calculated timeout is capped at 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n",
"The service enforces a maximum execution time limit to ensure fair device usage. This limit is capped at 3 hours to ensure fair device usage. If a `max_execution_time` is also specified for the job, the lesser of the two values is used.\n",
Comment thread
JJRBEST marked this conversation as resolved.
Outdated
"\n",
"For example, if you specify `max_execution_time=5000` (approximately 83 minutes), but the service determines it should not take more than 5 minutes (300 seconds) to execute the job, then the job is canceled after 5 minutes.\n",
Comment thread
JJRBEST marked this conversation as resolved.
Outdated
Comment thread
JJRBEST marked this conversation as resolved.
Outdated
"\n",
Expand Down