bigfile/zodb: Make auto format the default

If a user doesn't explicitly declare a ZBlk format, it can be assumed
that this user wants to have the best ratio between consumed storage space
and data access speed. Currently the best ratio between these two is
provided by the new 'auto' (heuristic) format. In case of small appends this
format helps reducing storage space, and in any other case it just
behaves like ZBlk0 [1]. Therefore this default ensures a fast access speed [2],
but also avoids a massive data growth in case of many small appends [3].

[1] An exception to this is: in its current implementation a block
behaves like ZBlk1 (slow access) in case it isn't fully filled up yet.

[2] As this was stated as a reason why ZBlk1 as a default format was
reverted in 0b68f178.

[3] This was perhaps the reason why ZBlk1 was set to be the default format
in 9ae42085. The massive
storage space consumption can already be a problem with few array to
which regularly small data is appended to, as it can easily happen with
Wendelin development instances.

/reviewed-by @kirr
/reviewed-on !20
51 jobs for master in 0 seconds
latest
Status Job ID Name Coverage
  External
passed Wendelin.core.UnitTest-ZODB5

00:29:54

passed Wendelin.core.UnitTest-ZODB5

00:27:00

passed Wendelin.core.UnitTest-ZODB5

00:23:49

passed Wendelin.core.UnitTest-ZODB5

00:27:02

passed Wendelin.core.UnitTest-ZODB5

00:29:32

passed Wendelin.core.UnitTest-ZODB5

00:28:05

passed Wendelin.core.UnitTest-ZODB5

00:28:28

passed Wendelin.core.UnitTest-ZODB5

00:29:13

passed Wendelin.core.UnitTest-ZODB5

02:51:37

passed Wendelin.core.UnitTest-ZODB5

02:42:18

passed Wendelin.core.UnitTest-ZODB5

00:24:57

passed Wendelin.core.UnitTest-ZODB5

00:31:00

passed Wendelin.core.UnitTest-ZODB5

00:28:57

passed Wendelin.core.UnitTest-ZODB5

00:30:00

passed Wendelin.core.UnitTest-ZODB5

01:04:57

failed Wendelin.core.UnitTest-ZODB5

00:00:36

failed Wendelin.core.UnitTest-ZODB5

00:00:23

failed Wendelin.core.UnitTest-ZODB5

00:00:31

failed Wendelin.core.UnitTest-ZODB5

00:00:33

failed Wendelin.core.UnitTest-ZODB5

00:00:21

failed Wendelin.core.UnitTest-ZODB5

00:00:38

failed Wendelin.core.UnitTest-ZODB5

00:00:27

failed Wendelin.core.UnitTest-ZODB5

00:00:29

failed Wendelin.core.UnitTest-ZODB5

00:00:30

failed Wendelin.core.UnitTest-ZODB5

00:00:27

failed Wendelin.core.UnitTest-ZODB5

00:16:29

passed Wendelin.core.UnitTest-ZODB5

00:26:42

passed Wendelin.core.UnitTest-ZODB5

00:26:43

passed Wendelin.core.UnitTest-ZODB5

00:24:36

passed Wendelin.core.UnitTest-ZODB5

00:24:59

passed Wendelin.core.UnitTest-ZODB5

00:25:48

passed Wendelin.core.UnitTest-ZODB5

00:26:25

passed Wendelin.core.UnitTest-ZODB5

00:28:49

passed Wendelin.core.UnitTest-ZODB5

00:30:18

passed Wendelin.core.UnitTest-ZODB5

00:30:02

passed Wendelin.core.UnitTest-ZODB5

00:45:15

passed Wendelin.core.UnitTest-ZODB5

00:23:40

passed Wendelin.core.UnitTest-ZODB5

00:26:25

passed Wendelin.core.UnitTest-ZODB5

00:43:36

passed Wendelin.core.UnitTest-ZODB5

00:28:16

passed Wendelin.core.UnitTest-ZODB5

03:26:00

passed Wendelin.core.UnitTest-ZODB5

00:27:59

passed Wendelin.core.UnitTest-ZODB5

03:53:23

passed Wendelin.core.UnitTest-ZODB5

00:29:17

passed Wendelin.core.UnitTest-ZODB5

00:26:37

passed Wendelin.core.UnitTest-ZODB5

00:36:31

passed Wendelin.core.UnitTest-ZODB5

00:28:48

passed Wendelin.core.UnitTest-ZODB5

01:10:28

passed Wendelin.core.UnitTest-ZODB5

00:24:52

passed Wendelin.core.UnitTest-ZODB5

00:28:20

passed Wendelin.core.UnitTest-ZODB5

00:29:23