@jprochazk/cbor - npm Package Compare versions

Comparing version 0.4.2 to 0.4.3

package.json

		{
		"name": "@jprochazk/cbor",
		"version": "0.4.2",
		"version": "0.4.3",
		"description": "Partial implementation of RFC 7049 (CBOR)",
		@@ -5,0 +5,0 @@ "author": "Jan Procházka",

README.md

		@@ -44,7 +44,8 @@ # cbor

		\| CPU \| CBOR.decode \| CBOR.encode \| CBOR.encodeInto \|
		\| :------- \| :------------ \| :------------ \| :-------------- \|
		\| i5-8600K \| 5225.64 ops/s \| 8998.11 ops/s \| 9268.09 ops/s \|
		\| Browser \| CBOR.decode \| CBOR.encode \| CBOR.encodeInto \|
		\| :------ \| :---------- \| :---------- \| :-------------- \|
		\| Chrome \| 5225 ops/s \| 8998 ops/s \| 9268 ops/s \|
		\| Firefox \| 20454 ops/s \| 22323 ops/s \| 22900 ops/s \|

		The JSON data used in the test is 2 KB decoded and 1.8 KB encoded. This means the library can decode at 13 MB/s and encode at 10 MB/s.
		Results are on a i5-8600k intel processor. The JSON data used in the test is 2 KB decoded and 1.8 KB encoded. This means the library can decode at 13 MB/s and encode at 10 MB/s.

		@@ -51,0 +52,0 @@ You can squeeze out a bit more performance if you use `CBOR.encodeInto` with a sufficiently large buffer. the `CBOR.encode` default is 1024 bytes, which should be enough for the vast majority of uses, but if you ever find yourself using more than that, utilize `CBOR.encodeInto`.

		@@ -44,7 +44,8 @@ # cbor

		\| CPU \| CBOR.decode \| CBOR.encode \| CBOR.encodeInto \|
		\| :------- \| :------------ \| :------------ \| :-------------- \|
		\| i5-8600K \| 5225.64 ops/s \| 8998.11 ops/s \| 9268.09 ops/s \|
		\| Browser \| CBOR.decode \| CBOR.encode \| CBOR.encodeInto \|
		\| :------ \| :---------- \| :---------- \| :-------------- \|
		\| Chrome \| 5225 ops/s \| 8998 ops/s \| 9268 ops/s \|
		\| Firefox \| 20454 ops/s \| 22323 ops/s \| 22900 ops/s \|

		The JSON data used in the test is 2 KB decoded and 1.8 KB encoded. This means the library can decode at 13 MB/s and encode at 10 MB/s.
		Results are on a i5-8600k intel processor. The JSON data used in the test is 2 KB decoded and 1.8 KB encoded. This means the library can decode at 13 MB/s and encode at 10 MB/s.

		@@ -51,0 +52,0 @@ You can squeeze out a bit more performance if you use `CBOR.encodeInto` with a sufficiently large buffer. the `CBOR.encode` default is 1024 bytes, which should be enough for the vast majority of uses, but if you ever find yourself using more than that, utilize `CBOR.encodeInto`.

New alerts