Does GetSize() poll the database or filesystem?

[evilpenguin]

Can't tell from the API docs, does the GetSize() pull its data from the database or does it have to hit the filesystem on every call?

[Slugger]

I assume we're talking file size queries? I'd guess it'd hit the filesystem APIs for that info based on the fact that it's rather quick to update that value while a file is recording. If it were in the database then the core would be constantly hitting the filesystem API and updating the database every second to keep the value current in wiz.bin. Since that'd be a massive waste of file i/o given that most of the time no one/nothing is requesting that info, I'd have to conclude the API call hits the filesystem directly on demand.

[GKusnick]

Seems like an easy question to answer by experimentation with ProcMon or something similar.

That said, unless caching the information in RAM is a documented part of the method's contract, you'd probably be wise to code as if it goes directly to the filesystem. You don't want to depend on behaviors that might just be accidents of the implementation and could change without warning.

[evilpenguin]

The reason I ask is that I need to find a quick/easy way to identify/filter a special video in a list. My original hope was to use the size since number comparisons are quick and I assumed it was pulling from the database rather than the file system.

But if that's not the case, which I suspect it isn't after some performance testing, I need to pick a new video characteristic to check for. GetMediaFileFormatDescription() should work pretty well too, I can make the format be strange enough that conflicts would be near impossible.

[GKusnick]

If these are videos you're creating, why not use SetMediaFileMetadata to label them with an explicit tag?

[evilpenguin]

Originally Posted by GKusnick

If these are videos you're creating, why not use SetMediaFileMetadata to label them with an explicit tag?

They're generated external to Sage so encoding that info into the video information seems like a nice, low-tech, workaround.

[GKusnick]

You could generate a .properties file to contain the custom metadata, and it will be imported into the database when Sage creates the MediaFile object.

[razrsharpe]

Originally Posted by evilpenguin

They're generated external to Sage so encoding that info into the video information seems like a nice, low-tech, workaround.

these aren't by any chance dummy mkv's created for your playon importer? I've been meaning to ask you how you identify and filter by them in diamond?

[PLUCKYHD]

Originally Posted by razrsharpe

these aren't by any chance dummy mkv's created for your playon importer? I've been meaning to ask you how you identify and filter by them in diamond?

In the current version we do it the same as SMM and by the playon directory location. The next version will be by the filesize to get it's source (ie netflix or hulu)

[Opus4]

Originally Posted by evilpenguin

Can't tell from the API docs, does the GetSize() pull its data from the database or does it have to hit the filesystem on every call?

In case there is still any question: GetSize() does get the actual file size, so I wouldn't use it if speed is a critical issue.

Example: for the detailed info menus, I fork a thread in the AfterMenuLoad hook to get the file size & then refresh the screen once that is done because otherwise there are cases where the UI could stop for a bit if that call were to be in the UI chain & it ended up taking a while to get the file size.

- Andy