Large Payload XML Warning

[vulcanjedi]

My actor payload is throwing this warning, any suggestions on filtering for this category?
Not sure I just updated to Kodi finally and latest VC after being lazy.
Love the new updates., Thanks James / Nimst3r!

[jitterjames]

Sounds like you need to delete some of those "B Movies".

Maybe you can filter it down to actors that appear in 2 or more movies?

[nime5ter]

If you want to try the filter that James suggests above, I *think* this query will work:

Code: [Select]

SELECT distinct idActor, strActor from actors WHERE idActor IN (select idActor from actorlinkmovie GROUP BY idActor HAVING COUNT(*)>1) ORDER BY strActor

[vulcanjedi]

Thanks Nime5ter, I have been trying to attempt James' suggestion however my repeated attempts this wknd have show my sql querying is apparently not a particular strength of mine.
Running the sql command directly from mysql  dropped the results by nearly 2/3rds!
I pasted your query but it fails in VC with the following for me?
...

---------------------------
Fatal error encountered during command execution.

SCANNING ABORTED

[jitterjames]

That sql was tested using the xSql plugin (sqlite) so you may need to adapt it to work in MySql.  We don't have a working MySQL setup at the moment so we can't do much in the way of testing over here.

Maybe someone else using MySql can pitch in... nudge nudge wink wink pegleg... 

[vulcanjedi]

That sql was tested using the xSql plugin (sqlite) so you may need to adapt it to work in MySql.  We don't have a working MySQL setup at the moment so we can't do much in the way of testing over here.

Maybe someone else using MySql can pitch in... nudge nudge wink wink pegleg... 

You guys continue to amaze. Thanks for the headsup about it being xSql vs Mysql.  Odd that I pasted directly in mysql prompt and it ran fine.  Took a while on the first attempt in mysql but when i looked back it did finish. In VC however it errors out  not sure if the plugin is timing out or something or query syntax could be optimized for mysql

[vulcanjedi]

You guys continue to amaze. Thanks for the headsup about it being xSql vs Mysql.  Odd that I pasted directly in mysql prompt and it ran fine.  Took a while on the first attempt in mysql but when i looked back it did finish. In VC however it errors out  not sure if the plugin is timing out or something or query syntax could be optimized for mysql

Not sure if the MusicVids is error, cause its' not selected, but if not then I may be right on the 'timing out'

[nime5ter]

Yes, it looks like the server is timing out during the query. It's not the music videos.

By the way, do you actually use the commands in VC that require the actors payload XML? Because obviously if you don't use those commands, you can just delete the "offending" commands.

I'm not saying you should do that. Just thought I'd mention it, in case it's relevant.

Maybe James can extend the timeout values in a future release of the plugin (he's not here right now, so I don't know). This is not my area. I can't tell from the error whether that's a timeout on the server side that's beyond VC's control or not.

[jitterjames]

I think you just have an unusually large number of movies.

How long does it take to execute the query directly on MySql?  I don't want to create a super long timeout (assuming that is even an option) because it could potentially cause freezing for people when they have other issues.

[PegLegTV]

I just tested nime5ter's Sql query and it worked for me, I have 227 movies and it said it found 2259 actors so at least we know the Sql query is correct, and works with MySql 

[jitterjames]

Thanks.

I guess I didn't realize how many actors Kodi indexes per movie.  It's quite a high ratio of actors to movies.

[vulcanjedi]

Yes I thought the actors volume was a lot more than it used to be as well. I typically prescrape my media with MediaCompanion to create NFOs and am sure to deselect actor scraping with that tool.
I guess I shouldn't wait too long to update my Windows // XBMC/Kodi // VoxCommando all at once, my roommate was out of town and I felt ambitious!
Hmm I just reran the query directly in mysql again and again its taking a long time. I wouldn't suggest altering the timeout too drastically as you suggest, perhaps optimizing this query will be more efficient, maybe I can ask some dba colleagues at work tomorrow.
I had to kill the query just now I would say it was taking over 2-3mins if it wasn't hung.
I just ran your original query and per mysql supposedly it took just 0.13 secs and I still cant reproduce how i managed to get the suggested query to return but when it did I reran it several times and after that it was much more akin to the response time of yours...odd.
UPDATE it just finished.... (6 min 29.32 sec) lol

[jitterjames]

Yes I thought the actors volume was a lot more than it used to be as well. I typically prescrape my media with MediaCompanion to create NFOs and am sure to deselect actor scraping with that tool.

It sounds like you are not interested in actors so I suggest you just delete the actor query row from your xMySql settings. Problem solved.

[nime5ter]

James came up with a good query this morning that may work better for you:

Code: [Select]

SELECT distinct idActor, strActor from actors WHERE idActor IN (select idActor from actorlinkmovie WHERE iOrder < 2)
This will create a list with the top 2 billed actors in your movies. We've also removed the "sort by", which really isn't necessary at all and may have contributed to your problem.

Try with this, and if it works well, you could consider increasing the iOrder number to include, say, the top 4 billed actors or so.

[jitterjames]

I just found this thread... 

http://voxcommando.com/forum/index.php?topic=1143.msg9590#msg9590

Looks like all of this has been covered including a 3rd option for an SQL query.