mirror of
https://github.com/compiler-explorer/compiler-explorer.git
synced 2025-12-27 14:04:04 -05:00
18 lines
762 B
Plaintext
18 lines
762 B
Plaintext
* separate execution endpoint
|
|
* pros:
|
|
* easy to see how many hits are coming in to execute vs just compile
|
|
* can potentially separate endpoint to different servers, rate limit, queue separately?
|
|
* maybe cache better as filters are unimportant (if cache at all)
|
|
* better separation of concerns
|
|
* ultimately allows for execute-only UI?
|
|
* cons:
|
|
* needs two POSTs in the client (probably not a problem)
|
|
* maybe complicates the UI? Toggle code, code/execute, execute?
|
|
|
|
POST /api/execute/<lang>/<compiler>
|
|
{ code: "", stdin: "", libraries, compile options } as per compile?
|
|
|
|
On disk compilation cache? could then separate stdin from compile? S3 put? md5sum? retention policy? redis? will that end up costing too much?
|
|
|
|
Execution queue?
|