Well, let's make it short:
Never ever think about using the current "hide" cronjob for hiding nodes at bigger sites.
The current hide cronjob fetches all content objects of a specific class defined in the content.ini, loads the datamap and checks if the date of the end time attribute is older than the current time.
Well, if you have 45.000 articles that could last some time... maybe a bit longer... maybe till the end of the days...
So, I've rewritten the cronjob. I only fetch the objects of the specific classes which are NOT hidden and I am using the attribute filter to get only the objects where the end date is bigger than 0 and smaller than the current time.
One only disadvantage of my cronjob: You MUST run the cronjob at a siteaccess where the site.ini has
(So, don't run it at your admin siteaccess)