| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Remove memory manager component from content layer | Tor Brede Vekterli | 2017-12-04 | 1 | -3/+0 |
| | | | | | | | | | | | | | | | We already have resource utilization tracking in both MessageBus and the search core. The memory manager has never been auto-scaled based on the hardware present and adds a _lot_ of complexity without having any known instances where it has actually saved the day. Removing it also removes a mutex on the message hot path. If we need such functionality in the future, should design a lock-free solution. Cleanup | ||||
| * | Update copyright headers | Jon Bratseth | 2017-06-14 | 1 | -1/+1 |
| | | |||||
| * | Revert "Update copyright headers" | Jon Bratseth | 2017-06-14 | 1 | -1/+1 |
| | | |||||
| * | Update copyright headers | Jon Bratseth | 2017-06-14 | 1 | -1/+1 |
| | | |||||
| * | Revert "Copyright header" | Jon Bratseth | 2017-06-13 | 1 | -1/+1 |
| | | |||||
| * | Copyright header | Jon Bratseth | 2017-06-13 | 1 | -1/+1 |
| | | |||||
| * | Publish | Jon Bratseth | 2016-06-15 | 1 | -0/+34 |
 |
index : vespa | |
| An engine for low-latency computation over large data sets |
| summaryrefslogtreecommitdiffstats |