Re: [infinispan-dev] Appending to file

2013-07-09 Thread Mircea Markus
On 28 Jun 2013, at 17:16, Radim Vansa wrote: > Hi, > > I was playing with efficient ways to write to append-only log and I have some > results below. This sounds a lot like what the loggers do, might be worth looking at some FileAppender impls for inspiration ;) > > I've used three impleme

Re: [infinispan-dev] Appending to file

2013-07-07 Thread Radim Vansa
- Original Message - | From: "Galder Zamarreño" | To: "infinispan -Dev List" | Sent: Friday, July 5, 2013 7:46:03 AM | Subject: Re: [infinispan-dev] Appending to file | | | On Jul 3, 2013, at 10:20 AM, Radim Vansa wrote: | | > | > | > | > I&#x

Re: [infinispan-dev] Appending to file

2013-07-05 Thread Galder Zamarreño
On Jul 3, 2013, at 10:20 AM, Radim Vansa wrote: > | > > | > I've used three implementations: one simply synchronizing the access and > | > calling force(false) after each write (by default 1kB). Second with > | > threads cooperating - every thread puts its data into queue and waits for > | > a

Re: [infinispan-dev] Appending to file

2013-07-05 Thread Galder Zamarreño
On Jul 3, 2013, at 10:20 AM, Radim Vansa wrote: > | > > | > I've used three implementations: one simply synchronizing the access and > | > calling force(false) after each write (by default 1kB). Second with > | > threads cooperating - every thread puts its data into queue and waits for > | > a

Re: [infinispan-dev] Appending to file

2013-07-03 Thread Radim Vansa
| > | > I've used three implementations: one simply synchronizing the access and | > calling force(false) after each write (by default 1kB). Second with | > threads cooperating - every thread puts its data into queue and waits for | > a short period of time - if then its data are still in the queu

Re: [infinispan-dev] Appending to file

2013-07-03 Thread Galder Zamarreño
On Jun 28, 2013, at 5:16 PM, Radim Vansa wrote: > Hi, > > I was playing with efficient ways to write to append-only log and I have some > results below. > > I've used three implementations: one simply synchronizing the access and > calling force(false) after each write (by default 1kB). Seco