scriptoriumadmin/featurebase
1
0
Fork 0
mirror of https://github.com/featurebasedb/featurebase.git synced 2026-10-07 11:27:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Address review comments

Browse source
This commit is contained in:
Alan Bernstein 2018-05-15 14:35:35 -05:00
parent 3bb140a45c
commit 537c0e160a
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/administration.md
View file

@ -28,7 +28,7 @@ Pilosa is a concurrent application written in Go and can take full advantage of
#### Disk
Even though the main dataset is in memory Pilosa does back up to disk frequently. We recommend SSDs--especially if you have a write heavy application.
Even though the main dataset is in memory Pilosa does back up to disk frequently. We recommend SSDs—especially if you have a write heavy application.
#### Network

2
docs/faq.md
View file

@ -18,7 +18,7 @@ Pilosa is not a database in the traditional sense. While Pilosa does store data
Pilosa sits on top of a data store or multiple data stores.
### How is Pilosa different than Elasticsearch since they are both indexes?
### How is Pilosa different from Elasticsearch since they are both indexes?
Elasticsearch is a search engine based on Lucene, and is therefore very good at indexing and searching large volumes of unstructured text. As it matures, Elasticsearch has continued to move into the analytics space, but its core data object is still the "document". Pilosa is specifically designed to index structured data and improve query speed. By representing data as the relationship between objects, and then storing those relationships in bitmaps, Pilosa can very efficiently search and compare many millions of data points while still maintaining a small memory footprint.