|
From: Nick M. <nm...@gm...> - 2012-08-21 14:44:58
|
All, I am currently exploring PostgresXC as a clustering solution for a project i am working on. The use case is a follows: - Time series data from multiple sensors - Sensors report at various rates from 50Hz to once every 5 minutes - INSERTs (COPYs) on the order of 1000+/s - No UPDATEs once the data is in the database we consider it immutable - Large volumes of data needs to be stored (one sensor 50Hz sensor = ~1.5 billion rows for a year of collection) - SELECTs need to run as quick as possible for UI and data analysis - Number of clients connections = 10-20, +95% of the INSERTs are done by one node, +99% of the SELECTs are done by the rest of the nodes - Very write heavy application, reads are not nearly as frequent as writes but usually involve large amounts of data. My current cluster configuration is as follows Server A: GTM Server B: GTM Proxy, Coordinator Server C: Datanode Server D: Datanode Server E: Datanode My question is, in your documentation you recommend having a coordinator at each datanode, what is the rational for this? Do you think it would be appropriate in my situation with so few connections? Would i get better read performance, and not hurt my write performance too much (write performance is more important than read)? Thanks, Nick |