Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Commits on Mar 8, 2010
  1. @felixge

    Add link to new v0.2 branch

    felixge authored
  2. @felixge

    Current status update

    felixge authored
Commits on Jan 27, 2010
  1. @felixge
  2. @felixge

    Finished load test

    felixge authored
    Also found a bug in remove(), fixed now.
  3. @felixge

    ensure _docs[] doesn't contain deleted docs when load()ing

    Aaron Heckmann authored felixge committed
    Signed-off-by: Aaron Heckmann <aaron.heckmann@gmacfs.com>
  4. @felixge

    Test for load()

    felixge authored
  5. @felixge

    Test case for e415f8

    felixge authored
Commits on Jan 22, 2010
  1. @felixge

    Feature: Memory-only support

    felixge authored
    It is now possible to create a memory-only dirty database by omitting
    the `filename` parameter of the constructor. This is useful for testing.
    
    See: http://github.com/felixge/node-dirty/issues#issue/1
  2. @felixge
Commits on Jan 15, 2010
  1. @felixge

    Removing wrong paste

    felixge authored
Commits on Jan 14, 2010
  1. @felixge

    Doc typos

    felixge authored
Commits on Jan 13, 2010
  1. @felixge

    More explanation what Dirty is

    felixge authored
  2. @felixge

    Added note about append only

    felixge authored
  3. @felixge

    Key value store, not id value

    felixge authored
    Damn you search & replace! : )
  4. @felixge
  5. @felixge
  6. @felixge

    Renamed 'key' to 'id'

    felixge authored
    Seems to be the accepted standard in the NoSQL community. Oh well ...
  7. @felixge

    Bug fixes for remove

    felixge authored
  8. @felixge

    Update docs

    felixge authored
    Added new benchmark results & docs for Dirty.remove()
  9. @felixge

    Support for remove + bug fixes

    felixge authored
    Adding remove required some rather serious underlaying changes.
    There might be a few bugs now, but things just got a lot faster
    and awesome!
Commits on Jan 12, 2010
  1. @felixge

    Reduced default flush interval to 10

    felixge authored
    Seems to have no impact on performance, but is very convenient!
  2. @felixge

    Unlink file after flush test

    felixge authored
  3. @felixge

    Added docs & license

    felixge authored
Commits on Jan 11, 2010
  1. @felixge

    Fixing small mistake in benchmarks

    felixge authored
    new Date() was executed on every loop by mistake, but it doesn't seem
    to have a measurable impact on the benchmark.
Commits on Jan 9, 2010
  1. @felixge

    Fix implied global

    felixge authored
Commits on Jan 8, 2010
  1. @felixge

    Made filter benchmark more honest

    felixge authored
    Now there is actual filtering happening, and we're still getting
    ~10mio. docs / sec processed. Need to start testing with only filtering
    through all records once, but that will take a lot of records for
    testing. After that there might still be some v8 optimizations which
    are screwing with the performance, but we're certainly getting closer
    to the truth here.
    
    975100 docs added in 10003ms
    flushed to disc, starting filtering ...
    
    Filtered 98485100 docs in 10066 ms 	(9783936 per sec)
  2. @felixge

    Rename Dirty.docs to Dirty._docs

    felixge authored
    Users should not access the document array directly.
  3. @felixge

    Less flawed benchmark for filtering.

    felixge authored
    The previous benchmark was not entirely fair as it was not accessing
    any properties of the filtered documents.
    
    This version accesses the ._key property of each element, but there is
    no actual filtering happening. When doing real filtering the performance
    should become aligned to the set() performance where the main bottleneck
    is pushing elements onto the array.
    
    Anyway, this being said, here are the new, less-flawed numbers:
    
    105800 docs added in 1009ms
    flushed to disc, starting filtering ...
    
    Filtered 25180400 docs in 1004 ms 	(12540040 per sec)
  4. @felixge

    Small fix

    felixge authored
  5. @felixge

    Only emit flush event if all docs are on disk

    felixge authored
    There was a bug causing the flush event to potentially emit while some
    documents were still in memory and not yet scheduled for flushing.
  6. @felixge
  7. @felixge
  8. @felixge

    I like singular

    felixge authored
  9. @felixge

    Use .dirty extension for dirty files

    felixge authored
    Also gitignore *.dirty
  10. @felixge

    Output that test is done

    felixge authored
Something went wrong with that request. Please try again.