You are here

v3.4.2 Rex processing extremely slow

7 posts / 0 new
Last post
glehel
Offline
Donator
Joined: 3 years
Last seen: 5 months
v3.4.2 Rex processing extremely slow

Hi everyone,

​I recently updated to version 3.4.2 and noticed a severe performance regression regarding Rex processing.

​I ran a test using the exact same XML dataset on both the old and the new versions, and the difference is massive:

  • v3.2.1: Completed in 2 minutes.
  • v3.4.2: Took 28 minutes.

​Despite the huge increase in processing time, the final output is identical. There is no difference in quality or data structure that would justify this 14x slowdown. It seems the new version is just burning resources without adding any value to the result.

​Has anyone else experienced this? Is this a known bug in 3.4.2 or is there a new configuration setting I might be missing?

​Thanks!

Blackbear199
Offline
Has donated long time ago
Joined: 10 years
Last seen: 4 months

strange indeed.
i have never seen rex take that amount of time.

i assume its a pretty big xml file as even 2 min is alot.
checked the changelog and the only difference from 3.4.1 and 3.4.2 is this..
- postprocess 3.4.2 
            fixed   : UpdateXmltv , operation max_elements , elements were split using a wrong separator . 
i cant see that having any impact on performance as probably 99% of users dont even use max_element option.

upload your rex.config.xml

 

glehel
Offline
Donator
Joined: 3 years
Last seen: 5 months

Do you mean that's the only change compared to 3.2.1?

Blackbear199
Offline
Has donated long time ago
Joined: 10 years
Last seen: 4 months

oh yes,alot of changes, i missed you said 3.2.1.
your best off to download the documented configuration files from the downloads page and read the rex one.
then ask questions.

in your bin(windows) bin.net(linux) folder there is a changelog.txt file if you want to go through the updates.
 

glehel
Offline
Donator
Joined: 3 years
Last seen: 5 months

Thanks for the info.

​I understand there have been many changes, but I still struggle to understand why the processing time would increase this drastically (from 2 to 28 minutes) for the exact same result.

​I am on Linux. For now, I will keep using the old version for Rex processing to maintain workflow speed. I just posted here to see if anyone else has encountered this specific performance drop or if it's an isolated case."

Blackbear199
Offline
Has donated long time ago
Joined: 10 years
Last seen: 4 months

the biggest change is separators.
example

old format with latest webgrab
<title>'title'{ ('productiondate')}</title>
result
<title>show title</title>
<title>(year)</title>
new
<title>'title( )'{('productiondate( )'}</title>
result
<title>show-title (year)</title>

have you check your xml data?
as u can see the separator makes a huge difference,if u have it incorrect your file size will be way larger from all the extra tags not to mention when viewed in epg viewer it wont be correct.

 

halikus
Offline
Donator
Joined: 10 years
Last seen: 5 months

Thanks BB, i googled the problem and AI had a link for the word separators that brought me here.  Your example helped me figure it out, i found the instructions in the rex xml a little difficult to decypher.  FWIW you are missing a (cosmetic) trailing bracket after productiondate, i used ( )')}

Log in or register to post comments

Brought to you by Jan van Straaten

Program Development - Jan van Straaten ------- Web design - Francis De Paemeleere
Supported by: servercare.nl