Reputation
361
Top tag
Next privilege 500 Rep.
Cast close & reopen votes
Badges
4 14
Newest
 Critic
Impact
~21k people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
Aug
26
awarded  Critic
Aug
26
revised Usage of NoSQL storage in Finance
added 282 characters in body
Aug
26
revised Usage of NoSQL storage in Finance
added 282 characters in body
Aug
26
revised Usage of NoSQL storage in Finance
added 282 characters in body
Aug
26
revised Usage of NoSQL storage in Finance
added 531 characters in body
Aug
26
revised Usage of NoSQL storage in Finance
added 531 characters in body
Aug
24
answered Usage of NoSQL storage in Finance
Aug
24
comment Usage of NoSQL storage in Finance
MongoDB is a poor choice for tick data. You will have to index by ticker name and then retrieving large amounts (anything > 10-20000 ticks) will have to query the index for all the atomized bits of your data. Cassandra, which is a column store, is infinitely better suited. It stores data in a column family so all the ticks for a ticker on sequentially stored on disk. I have moved from Mongo to Cassandra for precisely this reason and have seen my range queries on tick data (usually 500k ticks approximately) increase in speed by 20x.
Jul
24
awarded  Notable Question
Oct
31
revised Best way to store hourly/daily options data for research purposes
added 83 characters in body
Oct
31
revised Best way to store hourly/daily options data for research purposes
added 83 characters in body
Oct
29
revised Best way to store hourly/daily options data for research purposes
added 222 characters in body
Oct
29
answered Best way to store hourly/daily options data for research purposes
Sep
24
awarded  Autobiographer
Apr
20
awarded  Necromancer
Mar
9
awarded  Nice Question
Feb
28
awarded  Notable Question
May
22
awarded  Nice Question
Apr
11
awarded  Popular Question
Jan
18
awarded  Popular Question