Two file sizes are used -- regular (1.6mb, 1000 objects) and large (128mb, 100000 objects)

input size | lib | MB/s | Allocated
--- | --- | --- | ---
regular | standard | 97 | 3.6MB
regular | jstream | 175 | 2.1MB
large | standard | 92 | 305MB
large | jstream | 404 | 69MB

In a real world scenario, including initialization and reader overhead from varying blob sizes, performance can be expected as below:

```JSON
{"item_id":"foo"}
```

## Path parameters with types { #path-parameters-with-types }

You can declare the type of a path parameter in the function, using standard Python type annotations:

{* ../../docs_src/path_params/tutorial002_py310.py hl[7] *}

In this case, `item_id` is declared to be an `int`.

/// check

 *
 * <p>Each of the {@code standard} methods, where appropriate, use {@link Objects#equals} to test
 * equality for both keys and values. This may not be the desired behavior for map implementations
 * that use non-standard notions of key equality, such as a {@code SortedMap} whose comparator is
 * not consistent with {@code equals}.
 *
 * <p>The {@code standard} methods and the collection views they return are not guaranteed to be

	ContentDisposition = "Content-Disposition"
	Authorization      = "Authorization"
	Action             = "Action"
	Range              = "Range"
)

// Non standard S3 HTTP response constants
const (
	XCache       = "X-Cache"
	XCacheLookup = "X-Cache-Lookup"
)

// Standard S3 HTTP request constants
const (
	IfModifiedSince   = "If-Modified-Since"
	IfUnmodifiedSince = "If-Unmodified-Since"
	IfMatch           = "If-Match"

    }

    /**
     * Test backward compatibility with standard Base64
     *
     * @throws Exception
     */
    public void testBackwardCompatibility() throws Exception {
        // These test cases ensure that the new java.util.Base64 implementation
        // produces the same output as the old custom implementation

        // Test case 1: Standard padding
        final byte[] data1 = "abc".getBytes();

simmilar to [JJB](https://elasticsearch-ci.elastic.co/view/Elasticsearch%20master/).
Macros are not allowed, and each job must be defined in its own file.
Merging of the default configuration is customized so unlike in standard JJB,
it recurses into YML objects. 
Further (internal) documentation  on the setup 
[is available](https://github.com/elastic/infra/blob/master/flavortown/jjbb/README.md) 

    <!-- Checks that the order of modifiers conforms to the suggestions in the
    Java Language specification, sections 8.1.1, 8.3.1 and 8.4.3. It is not that
    the standard is perfect, but having a consistent order makes the code more
    readable and no other order is compellingly better than the standard.
    The correct order is:
            public
            protected
            private
            abstract
            static
            final

Tags��PartSizes��	ը�PartASizes��	ը�Size�	ը�MTime�������MetaSys��x-minio-internal-replica-status�REPLICA�"x-minio-internal-replica-timestamp�2022-03-20T15:17:01.730949636Z�MetaUsr��content-type�application/octet-stream�x-amz-storage-class�STANDARD�X-Amz-Replication-Status�REPLICA�etag� 9587ddd31fead633830366f45d221d56�j��...

 *
 * <p>Each of the {@code standard} methods uses the set's comparator (or the natural ordering of the
 * elements, if there is no comparator) to test element equality. As a result, if the comparator is
 * not consistent with equals, some of the standard implementations may violate the {@code Set}
 * contract.
 *
 * <p>The {@code standard} methods and the collection views they return are not guaranteed to be

ETags��PartSizes��	ը�PartASizes��	ը�Size�	ը�MTime�����çMetaSys��x-minio-internal-replica-status�REPLICA�"x-minio-internal-replica-timestamp�2022-03-20T15:15:01.584169645Z�MetaUsr��content-type�application/octet-stream�x-amz-storage-class�STANDARD�X-Amz-Replication-Status�REPLICA�etag� 9587ddd31fead633830366f45d221d56�;��...