BTC/LTC/DOGE/HVC/MNR/MAX clients syncing stats

Over in another thread...

Quote from: TheRealSteve on May 18, 2014, 03:37:39 PM

yeah, the blocks [for maxcoin] are smaller, so the overall size of the chain is less.. but there's still many more blocks to sync with, with associated overhead. I should run a desync test sometime and get some figures Wink

Figured I'd dump those figures here. Don't ask me to interpret any of it, it's mostly meaningless anyway as the biggest factor is actually how fast the peers you can connect to are. Some of the clients tried connecting to quite a few peers that were nonexistent at the time before finally connecting somewhere useful (as per the debug.log).

coin/data	Bitcoin	Litecoin	Dogecoin	Heavycoin	Mjollnircoin	Maxcoin
graphs

blocks
indices
start	300,874	567,606	222,889	49,215	8,350	283,095
end	301,598	570,109	227,752	52,056	11,446	292,114
behind	724	2,503	4,863	2,841	3,096	9,019
times
start	14/05/15 15:03:31	14/05/15 15:04:50	14/05/15 20:38:03	14/05/15 19:44:21	14/05/15 15:03:21	14/05/16 09:49:59
end	14/05/19 19:52:07	14/05/19 19:37:08	14/05/19 13:51:16	14/05/19 19:02:05	14/05/19 19:12:33	14/05/19 13:31:09
behind (d hh:mm:ss)	4d 04:48:36	4d 04:32:18	3d 17:13:13	3d 23:17:44	4d 04:09:12	3d 03:41:10
blocks/day	172	598	1,308	716	742	2,860
blocks/week	1,207	4,183	9,157	5,009	5,193	20,019

time
startup	14/05/19 21:49:44	14/05/19 21:29:08	14/05/19 15:35:19	14/05/19 20:55:23	14/05/19 21:11:31	14/05/19 22:13:31
sync start	14/05/19 21:52:58	14/05/19 21:30:51	14/05/19 15:35:29	14/05/19 20:55:37	14/05/19 21:11:39	14/05/19 22:13:45
startup overhead (hh:mm:ss)	0:03:14	0:01:43	0:00:10	0:00:14	0:00:08	0:00:14
sync end	14/05/19 22:01:07	14/05/19 21:38:01	14/05/19 15:51:47	14/05/19 21:03:29	14/05/19 21:15:28	14/05/19 22:32:08
sync diff (hh:mm:ss)	0:08:09	0:07:10	0:16:18	0:07:52	0:03:49	0:18:23
s/block @ 100,000bytes/s	2	0	0	0	0	0
sync time / week @ 100kB/s (h:mm:ss)	0:48:47	0:07:00	0:13:46	0:01:43	0:00:31	0:09:06
s/block @ actual	1	0	0	0	0	0
sync time / week @ actual (h:mm:ss)	0:13:35	0:11:59	0:30:42	0:13:52	0:06:24	0:40:48

CPU
user (h:mm:ss)	0:16:13	0:02:52	0:07:55	0:06:57	0:00:33	0:13:08
kernel (h:mm:ss)	0:02:15	0:00:57	0:00:37	0:00:38	0:00:42	0:01:47

HDD
reads	2,992,577	429,872	767,366	40,559	7,487	220,642
read bytes	26,565,148,411	3,754,144,908	6,795,639,585	278,190,592	50,746,399	1,623,264,498
writes	84,134	1,752,131	23,432	1,664,646	1,841,490	4,306,649
written bytes	3,414,357,297	1,063,227,109	1,595,999,329	111,349,188	20,538,143	630,196,047
blocks\	246,823,769	39,070,751	79,709,349	25,486,854	14,469,111	83,162,000
chainstate\	3,163,770,880	1,018,306,560	1,511,497,728	68,632,576	1,687,552	535,547,904
bytes/block	4,715,963	424,781	328,192	39,194	6,634	69,874

space (at end)
blocks	21,457,571,122	2,990,832,851	4,397,484,788	275,449,829	21,319,733	1,209,062,628
chainstate	518,350,174	412,237,903	328,322,397	29,271,429	1,779,804	105,167,348
total	21,975,921,296	3,403,070,754	4,725,807,185	304,721,258	23,099,537	1,314,229,976
blocks\ / block	71,146	5,246	19,308	5,291	1,863	4,139
chainstate\ / block	1,719	723	1,442	562	155	360
total / block	72,865	5,969	20,750	5,854	2,018	4,499

Network
connections (max)	12	8	9	8	4	19
connects	49	53	33	98	59	178
disconnects	21	16	7	9	11	31
sends	2,686	6,945	3,242	133	59	14,355
sent bytes	499,047	582,174	1,478,499	415,761	238,735	26,029,981
receives	39,748	15,238	24,466	3,363	909	18,485
received bytes	175,640,885	25,114,189	43,856,310	5,820,512	1,832,919	24,613,645
received bytes/s	359,184	58,405	44,843	12,332	8,004	22,315
received bytes/block	242,598	10,034	9,018	2,049	592	2,729
other bytes	53	23	19	10	3	137

HDD / Network
written blocks\ / received	1.405	1.556	1.818	4.379	7.894	3.379