search

laravel / horizon

Dashboard and code-driven configuration for Laravel queues.
https://laravel.com/docs/horizon
MIT License
3.88k stars 659 forks source link

Disable all jobs lists #1348

Closed andreladocruz closed 1 year ago

andreladocruz commented 1 year ago

Would be great if we had a way to disable all the lists (recent, pending, completed, failed, etc).

This consumes too much memory and in a heavily used system, this is not good at all.

driesvints commented 1 year ago

I think in this case you'd want a more capable server to serve these.

andreladocruz commented 1 year ago

@driesvints ,

Please do not talk about what you don't know.

We have our Google Cloud memorystore configured with 6GB only for queues.

At peak times we process more than 1.2 million jobs per hour.

These reports are completely useless for us and only consume memory that could be used by other jobs.

andreladocruz commented 1 year ago

@driesvints ,

We have all the logs we need in Google Cloud.

This kind of reply is unacceptable.

Xnip2023-11-18_18-34-09

Xnip2023-11-18_18-28-51 Xnip2023-11-18_18-29-19 Xnip2023-11-18_18-29-40

driesvints commented 1 year ago

I’m sorry if I offended you with my reply, that wasn’t my intention. If you want, you can always try a PR to see if it gets accepted 👍

andreladocruz commented 1 year ago

@driesvints ,

Your response was completely disproportionate and rude.

Regarding the issue of making a PR to "see" if it will be accepted, it is also inelegant.

I completely understand the issue of having logs available for smaller systems with fewer jobs.

However, for systems like ours, they don't make any sense precisely because they take up memory, making our operational costs higher than necessary.

To give you an idea, these logs make us maintain 6Gb of Redis only for the queues when our average usage is less than 1Gb.

The difference only applies to peak moments where, in addition to a large volume of jobs in our queues, we also have to manage useless histories and statistics.

I tried setting the "Jobs Triming Time" to zero, but the result was even worse and they were not removed.

We have been using the Laravel ecosystem in our project since 2017 and whenever we try to contribute our experience, we are disrespected by you.

What a beautiful "community" you are building.

driesvints commented 1 year ago

I tried to apologise here but it seems you're not interested in that. So feel free to move on.

andreladocruz commented 1 year ago

@driesvints ,

So it's like this, you respond rudely and I don't have the right to make that clear?

Don't I also have the right to explain the entire situation better, providing even more details about the issue?

All you have to say is "move on"?

It's not the first time you've responded this way and, based on your posture, you don't care.

I brought up an interesting question, to say the least, about better use of resources by this package.

An issue that, in my opinion, deserved a more in-depth conversation. After all, "artisans" like to do everything with excellence and refinement.

Once again you make it clear that opinions are only welcome if they agree with what you think.

Maybe I'm one of the few brave enough to tell you this.

Rest assured that I will "move on".

andreladocruz commented 1 year ago

@driesvints

just read this documentation:

https://redis.io/docs/management/optimization/memory-optimization/

Especially the "Memory allocation" topic.

andreladocruz commented 10 months ago

@driesvints and @taylorotwell ,

Can we restart this conversation?