[GemStone-Smalltalk] large blobs

James Foster james.foster at gemtalksystems.com
Tue Jun 17 14:28:59 PDT 2014

Hi John,

While GemStone/S is a database, there is some overhead in storing data in it as compared to the file system. In general, if you are dealing with large, static blobs, then I’d suggest that they be kept outside the database and referenced from some internal object. The internal representation can have a path and if you want to represent chunks of the file, you can have an object that has not just a path but a begin and end offset. Of course, if you want, you can just store a ByteArray in GemStone/S and everything would work fine.


On Jun 16, 2014, at 4:19 PM, John McIntosh <johnmci at smalltalkconsulting.com> wrote:

> Originally posted to the GLASS list, but suggested I repost to the gemstone list.
> I'm collecting thoughts on using gemstone to store large chunks of data (say JPGS).  Say 8 to 16MB in size. I have another case of blob data maybe upwards of 200MB but I'd store that in chunks just to enable better restart capabilities when pushing/pulling to a mobile device as that would need to restart a previously aborted transmission. 
> I'm wondering if anyone has had any experience with this? 
> -- 
> ===========================================================================
> John M. McIntosh <johnmci at smalltalkconsulting.com>
> Corporate Smalltalk Consulting Ltd. Twitter: squeaker68882
> ===========================================================================
> _______________________________________________
> GemStone-Smalltalk mailing list
> GemStone-Smalltalk at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/gemstone-smalltalk/attachments/20140617/51d739ce/attachment.html>

More information about the GemStone-Smalltalk mailing list