Hello,
I have been using Lager for several months now to much success. One
thing that I have not figured out though is how to get our output to
match that of what the limited documentation claims. According to
the blog post:
http://basho.com/blog/technical/201
The leveldb back end is not as fast as the default (bitcask), but leveldb does
not keep all keys in memory. So for a very large or unbounded set of keys
leveldb is superior. Leveldb stores values sorted by key, which also lets riak
speed up certain operations such as listing keys in a bucket.
Bryan,
You'll need to enable Lager's parse transform. The easiest way to do that is to
add the {parse_transform, lager_transform} to your compile options in
rebar.config.
Sean Cribbs
On Mar 31, 2012, at 3:13 AM, Bryan Hughes wrote:
> Hello,
>
> I have been using Lager for several months now
Actually, by default, the console doesn't show the 'verbose'
information. You should be able to see the extra information by looking
at the logfile, or you can enable it by changing the console config to
look like:
{lager_console_backend, [info, true]}
Hope that helps,
Andrew
__
Happy Saturday.
New code, slides, and more for today's Recap.
Enjoy.
Mark
twitter.com/pharkmillups
---
Riak Recap for March 28 - 31
=
1) Joseph Blomstedt's Erlang Factory Slides are online. His talk was
called, "Test First Construction of Di
I'm seeing very slow performance from Riak search even when querying
single terms, and I'd appreciate any advice on how to get insight into
where the time is going.
Right now, I'm using this function to time queries with the Erlang pb client:
TS =
fun (Pid, Bucket, Query) ->
T0 = now(),
{o
