"Erlang top got garbage"

[Benoit Chesneau <bc...@gmail.com>]

Hello all,

My test is simple a big db with 10000 docs on a node named 'server'
replicated to 100 dbs. on one another node named 'client'.  The replication
is launched on the node 'client' .

Before to speak about any performance results I wanted to watch on the
process with etop but can't do it due to a garbage issue:


Erlang top got garbage {trace_ts,<5258.30019.13>,out,
                                 {couch_replicator_api_wrap,receive_all,3},
                                 {1355,927385,29009}}
Erlang top got garbage {trace_ts,<5258.29906.13>,out,

 {couch_replicator_httpc,process_stream_response,5},
                           {1355,927385,29076}}
Erlang top got garbage {trace_ts,<5258.30115.13>,out,

 {couch_replicator_api_wrap,open_doc_revs,6},
                                 {1355,927385,29325}}
Erlang top got garbage {trace_ts,<5258.30046.13>,out,

 {couch_replicator_httpc,process_stream_response,5},
                           {1355,927385,29395}}


So it's happen during the multipart and response streaming.. Does anyone
see that too ?

- benoit