News for hackers. Stuff that matters.

A comment on Fast key-value stores: An idea whose time has come and gone. Parent comment

Re:Fast key-value stores: An idea whose time has come and gone by epistasis on Monday June 24, 2019 @11:38AM (#20264601)
> It seems to be based on this benchmark[1] which encodes a huge repeated int32 stuffed with random numbers

However, if your entire world consists of pushing around images to GPUs/TPUs, that's pretty much the only workload you ever need to optimize from your larger ops system.

Edit: not sure that this particular use case is exactly what's going on in that benchmark, now that I look more closely. Also, I wouldn't want to assert that it's a use case that matters a ton.

[ Parent | on HN ]
Re:Fast key-value stores: An idea whose time has come and gone by shereadsthenews on Monday June 24, 2019 @11:51AM (#20264787)
Encoding an image as a repeated sequence of variable-length integers would obviously be a poor choice.
[ Parent | on HN ]
Re:Fast key-value stores: An idea whose time has come and gone by rootlocus on Monday June 24, 2019 @01:03PM (#20265727)
Except.. that's pretty much how raw images are represented. Substituting "integers" for "bytes" if you want channel resolution, or leaving integers if you have 32bit pixel depth.

https://github.com/nothings/stb/blob/master/stb_image.h#L120

https://wiki.libsdl.org/SDL_Surface

[ Parent | on HN ]
Re:Fast key-value stores: An idea whose time has come and gone by pwodhouse on Monday June 24, 2019 @04:48PM (#20268308)
You overlooking the critical term: variable-length.
[ Parent | on HN ]
Re:Fast key-value stores: An idea whose time has come and gone by keymone on Monday June 24, 2019 @11:50AM (#20264771)
is anybody talking to GPU through memcached GETs/PUTs?
[ Parent | on HN ]