• Resolved joy0114

    (@joy0114)


    Hi,

    I’ve recently noticed that ccss generation has become extremely lazy…

    I understand that requests are made asynchronously, but I find that 45min to more than 2 hours between each retrieval of a file is a lot.
    Especially since, out of around 500 files, the first 400 were generated at a usual rate, but for the last 100, it takes several days to retrieve a few.
    I tried to detect the nodes again, no change.
    Forcing the cron, has no impact either.
    On this subject, we miss the modest but very useful page that showed the work in real time, when forcing the request.

    My report is:
    FAMNAPJP
    04/29/2025 08:47:58

    Thank you in advance for any ideas you may have.

    Best regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support litetim

    (@litetim)

    @joy0114 there have been changes for how many request are done per minute.
    I can’t say what’s the current rate.
    I will ask my QC colleagues and come back to you.

    One question:
    Is your cron added to run on server site? what’s the period it runs?

    Thread Starter joy0114

    (@joy0114)

    Hi litetim,

    Yes, cron is running on server (Litespeed Enterprise) and period for ccss request is each minute (chaque minute), that’s default setting:

    litespeed_task_ccss

    In 43 secondes
    Today at 3:05 pm Chaque minute LiteSpeed\CSS::cron_ccss()

    Usually, two ccss were generated each 2 minutes (period for my wp-cron.php cron task. So one/min. It was already slow, but now it’s very, very slow …
    Thank you in advance for your research.

    Best regards

    Plugin Support litetim

    (@litetim)

    @joy0114
    Please send me a report ID from LSC => Toolbox => Report => click on “Send to Litespeed”
    And please explain what do you mean by delay? Have you checked the QC cloud account and see the results?

    Thread Starter joy0114

    (@joy0114)

    Report is:

    TKSGBOMM
    Last Report Date: 04/29/2025 14:22:49

    ONE ccss is generated every 15, 30 min, sometimes 2 hours …

    my.quic.cloud account does not show errors: just ccss generated in 2-3-4 or 5 sec., but each one with an interval very variable, and not every 2 min (as it should be with my principal cron task – wp-cron.ph).

    I just switched from node19 to node12 with a new detection of nodes, I’m going to see if it’s better… but for now, it’s not.

    Litespeed plugin dashboard shows me for example:

    Dernier généré: il y a 57m 34s	
    Délai d’exécution de la demande précédente: 1s
    Demandes en file d’attente: 95 Forcer le cron
    Dernière demande: il y a 57m 33s

    Quickly translated:
    last generated 57m 34s ago
    execution delay: 1s
    In queue: 95
    last request: 57m 33s ago

    And “Forcer le cron” (force cron ask), does not seem to improve something.

    Some time ago, this opened a window showing in real time the number of ccss requested, and the number of files retrieved.
    It was so handy for checking correct operation.

    Thread Starter joy0114

    (@joy0114)

    Ok, I’ve purged the list of ccss to be processed, purged the css, then Purged All.
    On relaunching a crawl, the ccss generation seems to have restarted normally !

    So I think it’s solved. I don’t know why it was so laborious.

    Thanks for your help.
    Best regards

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘CCSS generating very lazy’ is closed to new replies.