allowEmpty = false,
        description =
            "Command line option for the performance test task to enable profiling. " +
                "For example `async-profiler`, `async-profiler-heap`, `async-profiler-wall`, `async-profiler-all` or `jfr`. Use `none` for benchmarking only.",
    )
}

object AdHocPerformanceScenarioLinux : AdHocPerformanceScenario(Os.LINUX)

        packet.opCode = NameServicePacket.WACK;
        packet.resultCode = NameServicePacket.SRV_ERR;
        packet.questionType = NameServicePacket.NBSTAT;
        packet.recordType = NameServicePacket.NBSTAT;
        expectedString =

pkg go/ast, func PackageExports(*Package) bool
pkg go/ast, func Print(*token.FileSet, interface{}) error
pkg go/ast, func SortImports(*token.FileSet, *File)
pkg go/ast, func Walk(Visitor, Node)
pkg go/ast, method (*ArrayType) End() token.Pos
pkg go/ast, method (*ArrayType) Pos() token.Pos
pkg go/ast, method (*AssignStmt) End() token.Pos
pkg go/ast, method (*AssignStmt) Pos() token.Pos

#### Framed protocols

Framed protocols like http/2 don't lend themselves to blocking APIs. Each application-layer thread wants to do blocking I/O for a specific stream, but the streams are multiplexed on the socket. You can't just talk to the socket, you need to cooperate with the other application-layer threads that you're sharing it with.

        Field opCodeField = NameServicePacket.class.getDeclaredField("opCode");
        opCodeField.setAccessible(true);
        opCodeField.set(nameQueryResponse, 7); // WACK opCode, which is not QUERY (0)

        // Ensure 'resultCode' is 0 for this test to isolate opCode condition
        Field resultCodeField = NameServicePacket.class.getDeclaredField("resultCode");

func registerBootstrapRESTHandlers(gm *grid.Manager) {
	server := &bootstrapRESTServer{}
	logger.FatalIf(serverVerifyHandler.Register(gm, server.VerifyHandler), "unable to register handler")
}

// client to talk to bootstrap NEndpoints.
type bootstrapRESTClient struct {
	gridConn *grid.Connection
}

// Verify function verifies the server config.

    // we try hard to make them robust in practice.  We could additionally try to add in a system
    // load timeout multiplier.  Or we could try to use a CPU time bound instead of wall clock time
    // bound.  But these ideas are harder to implement.  We do not try to detect or handle a
    // user-specified -XX:+DisableExplicitGC.
    //
    // TODO(user): Consider using

        long finish = System.currentTimeMillis();

        long time = finish - session.getRequest().getStartTime().getTime();

        String wallClock = session.getRequest().getDegreeOfConcurrency() > 1 ? " (Wall Clock)" : "";

        logger.info("Total time:  {}{}", formatDuration(time), wallClock);

        logger.info("Finished at: {}", formatTimestamp(finish));
    }

    @Override

And then, there would be another program (in some cases it's another program, in some cases it could be the same TLS Termination Proxy) that would talk to Let's Encrypt, and renew the certificate(s).

<img src="/img/deployment/https/https.drawio.svg">

The **TLS certificates** are **associated with a domain name**, not with an IP address.

The cashier gives you the number of your turn.

<img src="/img/async/concurrent-burgers/concurrent-burgers-04.png" class="illustration">

While you are waiting, you go with your crush and pick a table, you sit and talk with your crush for a long time (as your burgers are very fancy and take some time to prepare).