Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcement: New version coming soon #2302

Open
2 of 8 tasks
icleitoncosta opened this issue Aug 2, 2024 · 8 comments
Open
2 of 8 tasks

Announcement: New version coming soon #2302

icleitoncosta opened this issue Aug 2, 2024 · 8 comments

Comments

@icleitoncosta
Copy link
Contributor

icleitoncosta commented Aug 2, 2024

Hello everyone, I'm very excited to announce that we are working on version 2.0 of wppconnect.

This version will use Playwright as the browser orchestrator, allowing the use of different types of browsers. We've seen some performance improvements and also a significant enhancement in the project's ease of use. I'll share more details about it soon.

What I need to know from you right now is:

What would you like to see in version 2 of wppconnect?

  • Standard in the creation of all functions, using classes and models
  • Improvement in resource consumption of browsers, reducing memory usage.
  • Support for Proxies
  • Support for see status session (ram, cpu, etc) (WPP-Manager)
  • Change base do Playwight
  • Support for Custom packname and author for Stickers
  • Subscribe presence, unsubscribe improovment (WAJS)
  • Support for manage indexedDB and restore by other ways
@icleitoncosta icleitoncosta pinned this issue Aug 2, 2024
@Saifallak
Copy link

  • Resource consumption of each session?

@icleitoncosta
Copy link
Contributor Author

  • Resource consumption of each session?

Yes, definitely, I'm studying a way to significantly reduce the browser's consumption, so that WhatsApp itself consumes very few resources, only what's necessary, along with a configuration to change that.

@Saifallak
Copy link

  • Resource consumption of each session?

Yes, definitely, I'm studying a way to significantly reduce the browser's consumption, so that WhatsApp itself consumes very few resources, only what's necessary, along with a configuration to change that.

Great that would be awesome, but i meant a way to return each session consumption,

I mean session X consumption 200MB Ram 12% CPU
Session Y consumption 400MB ram 1% cpu

So i can monitor which sessions uses more resources.

@icleitoncosta
Copy link
Contributor Author

  • Resource consumption of each session?

Yes, definitely, I'm studying a way to significantly reduce the browser's consumption, so that WhatsApp itself consumes very few resources, only what's necessary, along with a configuration to change that.

Great that would be awesome, but i meant a way to return each session consumption,

I mean session X consumption 200MB Ram 12% CPU Session Y consumption 400MB ram 1% cpu

So i can monitor which sessions uses more resources.

Ahh, I see. I'll add this to our to-do list. I'm not sure if it's possible via Puppeteer, but we're working behind the scenes on the WPPConnect Manager, which will allow you to manage sessions, create new ones, etc. We can add something to monitor resources just like Grafana does.

@Saifallak
Copy link

  • Resource consumption of each session?

Yes, definitely, I'm studying a way to significantly reduce the browser's consumption, so that WhatsApp itself consumes very few resources, only what's necessary, along with a configuration to change that.

Great that would be awesome, but i meant a way to return each session consumption,
I mean session X consumption 200MB Ram 12% CPU Session Y consumption 400MB ram 1% cpu
So i can monitor which sessions uses more resources.

Ahh, I see. I'll add this to our to-do list. I'm not sure if it's possible via Puppeteer, but we're working behind the scenes on the WPPConnect Manager, which will allow you to manage sessions, create new ones, etc. We can add something to monitor resources just like Grafana does.

Great, also maybe use playwright instead of puppeteer https://playwright.dev/ ?

@icleitoncosta
Copy link
Contributor Author

  • Resource consumption of each session?

Yes, definitely, I'm studying a way to significantly reduce the browser's consumption, so that WhatsApp itself consumes very few resources, only what's necessary, along with a configuration to change that.

Great that would be awesome, but i meant a way to return each session consumption,
I mean session X consumption 200MB Ram 12% CPU Session Y consumption 400MB ram 1% cpu
So i can monitor which sessions uses more resources.

Ahh, I see. I'll add this to our to-do list. I'm not sure if it's possible via Puppeteer, but we're working behind the scenes on the WPPConnect Manager, which will allow you to manage sessions, create new ones, etc. We can add something to monitor resources just like Grafana does.

Great, also maybe use playwright instead of puppeteer https://playwright.dev/ ?

Yes, yes, we are switching to Playwright now, as it allows for a variety of browsers. It was just out of habit that I mentioned Puppeteer, haha.

@albertojrigail
Copy link

Hi, a lot of these features would be extremely helpful for us as we're currently experiencing issues that would be fixed by this new update. What's your timeline? Would be helpful to know. Thanks.

@gekkedev
Copy link
Contributor

gekkedev commented Oct 4, 2024

Support for Proxies

There is a PR to provide this in 1.X: #2354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants