Re: Persisting ContentCache to disk between sessions
With your suggestion, every new company onboarded will download the entire sprite. Sure it's only one image but it's 1500+ x 200px square. Our current architecture just downloads the single image that's new or changed at about 500 bytes.
Using a sprite is definitely an interesting option for down the road, perhaps only downloaded on launch and then update individual images on updates, but I have to get back to higher priority work.
Thanks for sharing.
On Oct 29, 2018, at 5:07 PM, Javier Guerrero García <javi.gg@xxxxxxxxx> wrote:
You're welcome, but... what's the exact problem with spriting in that
scenario? You could generate the sprite bitmap dynamically at any given
time (just paste every known logo one below another), even with bare PHP
(or needless to say with ImageMagic libraries), and then just poll for the
last modified date of the generated sprite bitmap :-?
On Mon, Oct 29, 2018 at 10:48 PM Erik Thomas <erikjthomas@xxxxxxxxxx> wrote:
> Hi Javier:
> The thing is we have 52 investor groups in 26 countries on 3 continents
> and they each have admins entering information that is then displayed in
> our app. Part of that information are companies that are presenting at
> regular investor meetings in these different countries. These companies all
> have logos. Our app polls for changes every 20 seconds, and if someone has
> added a new company, all users worldwide will see it appear in the app
> within 20 seconds.
> But thanks for your suggestion!
> On Oct 29, 2018, at 1:30 PM, Javier Guerrero García <javi.gg@xxxxxxxxx>
> Just my 2 cents: have you considered getting rid of everything and just use
> one sprite image for all the logos?
> You minimize connections to just 1 download, that if properly compressed
> and if logos share a fair amount to colors, could get the size per logo to
> a ridiculously few bytes. All item renderers would use the same image (100%
> bitmapCache hits), but at the cost of downloading the whole bitmap each
> time one of the logos change (how often?).
> It could be a fairly simple solution, and may it can improve your app
> responsiveness without too much trouble.
> Hope it helps ;-)
> On Mon, Oct 29, 2018 at 6:22 PM Erik Thomas <erikjthomas@xxxxxxxxxx>
>> Thanks everyone for your ideas.
>> Alex, I already knew how to do the serialization by encoding/decoding,
>> I may go down that path someday, but if FileStream would just serialize a
>> ContentCache (seems like a common want), it would have been a quick
>> improvement to app responsiveness.
>> Having to write my own serializing logic pushes this down on our
>> priorities list since improving app responsiveness is more of a "nice to
>> have" and not a high priority.
>> I'm going to drop this idea for now.
>> Thanks again for your insights, everyone.