google cloud datastore partitioning strategy -


trying use google cloud datastore store streaming data iot devices. getting data 10,000 devices @ rate of 2 rows (entities) in 1 minute per device. data entities never updated purged @ regular interval. backend code in php.

  1. do need partition data better performance @ present in mysql table. using table partitions based on key.

  2. if yes, should used use namespaces 1 namespace 1 device or should create 1 kind 1 device such "device_data_1", "device_data_2"

thanks

no, not need partitioning, datastore performance not impacted number or entities being written or read (as long they're not in same entity group, has overall write rate of 1/sec).

see these somehow related answers: does google datastore have provisioned capacity system dynamodb?


Comments

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

python Tkinter Capturing keyboard events save as one single string -

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -