| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Read 2 bytes instead of one at the start of load_segment_entries. This makes ↵ | Matthew Sackman | 2009-12-11 | 1 | -11/+4 |
| | | | | | the code cleaner and avoids a further read in the case of a del or ack | ||||
| * | cosmetic | Matthias Radestock | 2009-12-06 | 1 | -11/+8 |
| | | |||||
| * | cosmetic and some refactoring | Matthias Radestock | 2009-12-04 | 1 | -86/+77 |
| | | |||||
| * | appropriately renamed | Matthew Sackman | 2009-12-04 | 1 | -6/+6 |
| | | |||||
| * | cough, splutter, sneeze etc | Matthew Sackman | 2009-12-04 | 1 | -1/+1 |
| | | |||||
| * | segments now stored in array, not dict | Matthew Sackman | 2009-12-04 | 1 | -95/+93 |
| | | |||||
| * | cosmetic | Matthias Radestock | 2009-12-04 | 1 | -3/+3 |
| | | |||||
| * | refactoring | Matthew Sackman | 2009-12-04 | 1 | -34/+39 |
| | | |||||
| * | combined steps 3 and 4 of init, and made segment_find have the same type as ↵ | Matthew Sackman | 2009-12-04 | 1 | -75/+78 |
| | | | | | dict:find. Dropped the Dir from the Segments, and added find_segment_or_new/3 | ||||
| * | cosmetic | Matthias Radestock | 2009-12-03 | 1 | -13/+11 |
| | | |||||
| * | What a difference, two characters make... | Matthew Sackman | 2009-12-03 | 1 | -1/+1 |
| | | |||||
| * | Make the arrays fixed size and tell them the max size. The don't actually ↵ | Matthew Sackman | 2009-12-03 | 1 | -1/+1 |
| | | | | | take this much space initally, but it makes them a bit faster as they can make more sensible balancing decisions, we think. | ||||
| * | Switched to using array instead of dict for the inner journal. It's about ↵ | Matthew Sackman | 2009-12-03 | 1 | -70/+72 |
| | | | | | 10% faster. | ||||
| * | If I write it this way then it saves code and is maybe slightly faster. maybe. | Matthew Sackman | 2009-12-03 | 1 | -30/+22 |
| | | |||||
| * | merge heads | Matthew Sackman | 2009-12-03 | 1 | -7/+7 |
| |\ | |||||
| | * | cosmetic | Matthias Radestock | 2009-12-03 | 1 | -7/+7 |
| | | | |||||
| * | | Abstracted the segment caching in the qi, and associated improvements as not ↵ | Matthew Sackman | 2009-12-03 | 1 | -119/+131 |
| |/ | | | | all the state needs to be passed around all the time. | ||||
| * | Some renaming in the fhc and associated changes in qi and ms. | Matthew Sackman | 2009-12-03 | 3 | -20/+24 |
| | | |||||
| * | source code file compression | Matthew Sackman | 2009-12-03 | 1 | -6/+5 |
| | | |||||
| * | cosmetic | Matthias Radestock | 2009-12-02 | 1 | -6/+7 |
| | | |||||
| * | Up to 11kHz persistent on my home machine. Still a little way off the 13kHz ↵ | Matthew Sackman | 2009-12-02 | 2 | -30/+106 |
| | | | | | that I was getting before, but there were bugs in the previous QI (eg missing syncs) which could well have led to the old version being too fast. Added two functions to fhc: delete/1 which deletes without flushing any data at all. It will refuse to delete if the file isn't open; discard_write_buffer/1 which does what it says. We use the latter after scattering the journal as after we hit each segment, we sync the segment, so at that point there's no need at all to force out the data in the fhc for the journal prior to truncation. | ||||
| * | Allowed the journal to grow substantially bigger. This helps performance ↵ | Matthew Sackman | 2009-12-02 | 1 | -1/+1 |
| | | | | | substantially. | ||||
| * | New qi in place, tested and debugged. It works. It's not quite as fast as ↵ | Matthew Sackman | 2009-12-02 | 4 | -1460/+594 |
| | | | | | before because of use of nested dicts. This can be solved by using sets for publishes, deliveries and acks within each segment - we don't actually need what the dict provides and sets will go much faster. That change should be fairly straight forward to do - the code will get a little longer, but not much more complex. | ||||
| * | Finished. It might work - untested though | Matthew Sackman | 2009-12-02 | 1 | -35/+217 |
| | | |||||
| * | More good progress on qi3. The code still almost looks pretty in places. Its ↵ | Matthew Sackman | 2009-12-02 | 1 | -7/+175 |
| | | | | | prettiness is not diminishing. | ||||
| * | Lots of good progress on qi3. The code almost looks pretty in places | Matthew Sackman | 2009-12-02 | 1 | -36/+377 |
| | | |||||
| * | Wrote two key combinators which will be used by the new queue index shortly. ↵ | Matthew Sackman | 2009-12-01 | 1 | -0/+159 |
| | | | | | qi3 is very temporary | ||||
| * | Only pull in one segment at a time from γ into q3 | Matthew Sackman | 2009-11-30 | 1 | -8/+9 |
| | | |||||
| * | Remove the garbage_collect call as this doesn't seem to be necessary in R13B03 | Matthew Sackman | 2009-11-30 | 1 | -3/+1 |
| | | |||||
| * | Garbage collect on memory reduction; remove delayed_write in queue index as ↵ | Matthew Sackman | 2009-11-30 | 3 | -4/+8 |
| | | | | | we're handling buffering ourselves; add a hack to get the raw vq status out of rabbitmqctl | ||||
| * | Removal of unnecessary clause in handle_info for queue process as prefetcher ↵ | Matthew Sackman | 2009-11-27 | 2 | -9/+4 |
| | | | | | has gone. Bump rabbit supervisor to allow all processes to take as long as necessary to exit. This should ensure cached data gets flushed out. | ||||
| * | Removed mnesia table and dq_msg_loc record that's no longer needed | Matthew Sackman | 2009-11-27 | 2 | -12/+5 |
| | | |||||
| * | There was a bug. Now it has gone away. It arose when γ has a partial ↵ | Matthew Sackman | 2009-11-27 | 3 | -39/+116 |
| | | | | | segment, and then memory is made available, and the next msg is persistent. It will go into the partial segment in qi, but will also be in q1 in vq. This lead to the msg being duplicated. Solution is to track the max seq id beyond the end of the γs, and thus drop anything being returned in the segment from qi with a seq_id above this max seq id. | ||||
| * | storage_mode is long gone | Matthias Radestock | 2009-11-27 | 1 | -1/+1 |
| | | |||||
| * | unintended variable capture | Matthias Radestock | 2009-11-27 | 1 | -6/+7 |
| | | |||||
| * | s/full_flush_journal/flush_journal and some refactoring | Matthias Radestock | 2009-11-26 | 4 | -56/+41 |
| | | |||||
| * | better const names | Matthias Radestock | 2009-11-26 | 1 | -17/+17 |
| | | |||||
| * | cosmetic | Matthias Radestock | 2009-11-26 | 1 | -33/+41 |
| | | |||||
| * | cosmetic and inlining | Matthias Radestock | 2009-11-26 | 1 | -33/+33 |
| | | |||||
| * | use ?SERVER wherever possible | Matthias Radestock | 2009-11-26 | 1 | -1/+1 |
| | | |||||
| * | Don't demonitor if we received a DOWN msg. | Matthew Sackman | 2009-11-26 | 1 | -6/+10 |
| | | |||||
| * | remove unnecessary comment | Matthew Sackman | 2009-11-26 | 1 | -3/+0 |
| | | |||||
| * | Added demonitoring, corrected counting on deregistering, and got fed up with ↵ | Matthew Sackman | 2009-11-26 | 1 | -43/+49 |
| | | | | | the lack of whitespace | ||||
| * | Don't need this variable anymore | Matthew Sackman | 2009-11-26 | 1 | -2/+1 |
| | | |||||
| * | Remove the small_duration_threshold, and instead smooth the ram_msg_count ↵ | Matthew Sackman | 2009-11-26 | 2 | -38/+16 |
| | | | | | over the last two periods. This seems to work reasonably well. | ||||
| * | SMALL_INFINITY_OSCILLATION_DURATION => SMALL_DURATION_THRESHOLD | Matthew Sackman | 2009-11-26 | 1 | -9/+8 |
| | | |||||
| * | s/b(.)t/s\1m/ | Matthew Sackman | 2009-11-26 | 1 | -1/+1 |
| | | |||||
| * | Improved documentation and code regarding fast moving mainly empty queues ↵ | Matthew Sackman | 2009-11-26 | 1 | -35/+59 |
| | | | | | and the SMALL_INFINITY_OSCILLATION_DURATION definition. Oh, and clamped zero. | ||||
| * | beautifuler | Matthew Sackman | 2009-11-26 | 1 | -5/+2 |
| | | |||||
| * | Improvements to documentation, further improvements to conditional and ↵ | Matthew Sackman | 2009-11-26 | 1 | -33/+32 |
| | | | | | refactorings. Removal of max queue duration because the rate calculated by the queue doesn't decay in the way necessary to make the max queue duration necessary | ||||
