TryDesync: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* The host is a VM. | * The host is a VM. | ||
* The host usually runs a development snapshot that may be unstable. You "get" to help us test, Aperture Science style. | |||
* The host kernel has various debugging facilities enabled, which hurts performance. | |||
* Network connections are limited in terms of concurrency. | * Network connections are limited in terms of concurrency. | ||
* Network traffic is limited in aggregate throughput. | * Network traffic is limited in aggregate throughput. | ||
Revision as of 17:48, 17 November 2025
About try.desync.com
try.desync.com gives you a web-based shell on a dynamically-allocated instance.
There are some differences from a normal instance, though. Specifically:
- The host is a VM.
- The host usually runs a development snapshot that may be unstable. You "get" to help us test, Aperture Science style.
- The host kernel has various debugging facilities enabled, which hurts performance.
- Network connections are limited in terms of concurrency.
- Network traffic is limited in aggregate throughput.
- The Basis image is a customized FreeBSD that includes some tools like curl and mtr.
- SSH host keys are pre-generated (and thus, shared) to reduce startup time.
- The broker's SSH keys are preloaded, rather than having to wait for desync-provision to run.
The session broker (Zuul) places some limits on number of concurrent sessions beyond the normal placement limits imposed by the API, mostly by client ASN and/or subnet. The idea is to prevent one person from hogging all the sessions, which might also indicate that some mischief is afoot.