Mass user authentication with ROM-in-RAM: demo On 2x E5-2670 (16 cores, 32 threads) with 128 GB RAM (8x DDR3-1600) 112 GB ROM initialization takes half a minute (on server bootup) yescrypt's TMTO-resistant algorithm discourages recomputation on smaller machines ROM is maintained in a SysV shared memory segment This is one good way to do it, although yescrypt API does not mandate it Thus, there's no delay in our demo "authentication service" (re)start Important for ease of system administration, and to minimize downtime yescrypt is passed a pointer to the ROM via an appropriate API Request rate capacity may be tuned, with varying RAM usage settings Attacker's cost varies by our usage of: CPU time, RAM, bandwidth, and by ROM size