ll try is to resolve sibling during write but I
hoped I can avoid/delay that until read happens.
This vclock/storage/bandwidth explosion really surprised me.
Regards
Daniel
--
View this message in context:
http://riak-users.197444.n3.nabble.com/Clarifying-withoutFetch-with-LevelDB-and-tp40330
fields)
> and that did not made any difference, still 25-38MB/s write to level db per
> node.
>
> D.
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/Clarifying-withoutFetch-with-LevelDB-and-tp4033051p4033053.html
> Sent fro
changed.
I also disabled 2i indexes that I thought may matter (four 16 bytes fields)
and that did not made any difference, still 25-38MB/s write to level db per
node.
D.
--
View this message in context:
http://riak-users.197444.n3.nabble.com/Clarifying-withoutFetch-with-LevelDB-and-tp4033051p4033053
r will I be bitten by
> something?
> How to explain high number of MB written to disks?
>
> Regards
> Daniel
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/Clarifying-withoutFetch-with-LevelDB-and-tp4033051.html
> Sent fro
--
View this message in context:
http://riak-users.197444.n3.nabble.com/Clarifying-withoutFetch-with-LevelDB-and-tp4033051.html
Sent from the Riak Users mailing list archive at Nabble.com.
___
riak-users mailing list
riak-users@lists.basho.com
http:
