What's the scariest thing you can see just before a game?

[kbs666]

It's a combination of alot of things. The images are all resized per the guidelines Realm Works throws at me when it errors. There is alot of images though. Monsters, npcs, locations, overlay maps. Then there is a huge amount of snippets. Of course the database of audio clips probably doesn't help either.

Don't worry about the text. In this sort of thing text is functionally irrelevant.

A fairly standard and reliable rule of thumb is a page of plain text in HTML is probably about 1k of storage.

What eats up storage is images and audio. I haven't looked too closely at Syrinscape but if it stores every clip in the RW DB, which it probably has to, that could blow up a realm really fast.

 

[daplunk]

It's not Syrinscape. That manages the sound itself. Pretty sure that downloads as it plays.

The sound is all local files. Absolutely part of the problem but also having it all in Realm Works is the attraction of the program in the first place.

 

[Avi]

Syncing is incremental (changes only) so the size should not be a problem only the amount of changes.
So either that's not the issue, or the compare/synch mechanism needs a hard look by LWD.
If I understood correctly (BIG if ) originally the intention was to do the compare server side, in order to support all kinds of funky merge scenarios. Maybe with the change in the way the Market will work this has to be looked at as well?
(my background is MS SQL server so Replication - Push/Pull/Subscribe come to mind, not sure if any of these is implemented in Firebird)
I'm sure Rob is having plenty on his plate, but will get to it at some point...

 

[Joe]

What eats up storage is images and audio. I haven't looked too closely at Syrinscape but if it stores every clip in the RW DB, which it probably has to, that could blow up a realm really fast.

Syrinscape stores all it's own sounds. None of that is in the Realm Works database. The only data stored on our end is URI links to play Syrinscape sounds. If Syrinscape is not installed, or if Syrinscape doesn't have that soundset available for some reason (not downloaded, not purchased on that Syrinscape account, etc), the link will do nothing when clicked in Realm Works.

So we do store some data, but it is a minuscule link that's only a few dozen characters of text to serve as a link into Syrinscape, not the complete sound files themselves.

 

[rob]

Syncing is incremental (changes only) so the size should not be a problem only the amount of changes.
So either that's not the issue, or the compare/synch mechanism needs a hard look by LWD.
If I understood correctly (BIG if ) originally the intention was to do the compare server side, in order to support all kinds of funky merge scenarios. Maybe with the change in the way the Market will work this has to be looked at as well?
(my background is MS SQL server so Replication - Push/Pull/Subscribe come to mind, not sure if any of these is implemented in Firebird)
I'm sure Rob is having plenty on his plate, but will get to it at some point...

The issue that @daplunk got into was what we call a "sync conflict". Basically, Realm Works thinks that here are changes waiting on BOTH the client and server. At that point, the only option is to pick one to keep and then send everything up/down to the other end for a complete overwrite. That obviously necessitates everything being transferred, which can take a very long time for a multi-gigabyte realm, depending on transfer speeds and server load.

Edit: Normally, the only data transferred is whatever has actually changed, which is pretty fast.

 

[daplunk]

Yeah standard syncing is fine... Which is why this is a scary message to see Usually a couple of minutes max depending on how out of control I get with the 'just one more article'...