> Where can I send you mail? My e-mail is ...
I'll ping you
On Wed, 27 Mar 2019 at 15:12, Shweta Sharma wrote:
> Thanks again Marc. Yes Deserialization code is as you listed below. I was
> using protobuf-net 2.4.0.0 but then moved to older version currently being
> used across our code base,
Thanks again Marc. Yes Deserialization code is as you listed below. I was
using protobuf-net 2.4.0.0 but then moved to older version currently being
used across our code base, 2.0.0.668, to see any impact. Where can I send
you mail? My e-mail is shwetad...@gmail.com. I can get these objects
> using StackExchange.Redis MGET
Yeah, there's really no way for me to dodge this, is there? ;p
Minor note: your parallel code currently doesn't actually allow any
meaningful parallelism - you *might* want to move the "lock" so that you
only "lock" around the "Add". You're also currently doing a
Big Thanks Marc for helping me here.
Question: how fast is "fast enough" here, and how big are your payloads?
Answer: < 50 ms for read and deserialization for 20K keys. Payload varies
depending on SubObj array length but in avg case SubObj array length does
not exceed 100 elements.
I am
Hi; I'd love to help you on this - I'm the protobuf-net author, and I also
know more than a little about redis; it *might* be a little off-piste for
this group though. Running some tests locally with 5000 instances, I get
times like 1ms, but it might be that I'm misunderstanding your object
model.
I am prototyping an application to store data in redis using
StackExhange.Redis client. I am using Protobuf for serializing my objects
and storing them as key/value pair in redis. When reading 20K keys using
pipeline (splitting keys in batches of 5000), I observe deserialization
times in