8000 layers.init cost too much time · Issue #101 · google/gopacket · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

layers.init cost too much time #101

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Open
bronze1man opened this issue Aug 6, 2015 · 6 comments
Open

layers.init cost too much time #101

bronze1man opened this issue Aug 6, 2015 · 6 comments

Comments

@bronze1man
Copy link
bronze1man commented Aug 6, 2015 •
edited
Loading

layers.init cost about 0.2s to init.

Make it lazy init or manually init should be good.
Make it faster is also an option.
But this kind of change will break the exist clients.
@gconnell
Copy link
Collaborator
gconnell commented Aug 6, 2015

Can you define "too much"? What's your threshold for # of cycles or total time?

@gconnell
Copy link
Collaborator
gconnell commented Aug 6, 2015

Also, what type of hardware are you running on?

@bronze1man
Copy link
Author

The threshold of the total time of program init is 0.1s.
When restart the server ,the init should quick so that the use will not disturb.
I am using a mac with 4 core 1.4GHz i5 cpu.

@hlandau
Copy link
hlandau commented Nov 28, 2015

I'm also experiencing this issue.

layers is consumed by a multicall binary which also provides commands which should execute quickly.
Making this initialization lazy would be nice.
Would you accept a PR for this?

@gconnell
Copy link
Collaborator

Sure thing!

On Sat, Nov 28, 2015 at 7:27 AM, Hugo Landau notifications@github.com
wrote:

I'm also experiencing this issue.

layers is consumed by a multicall binary which also provides commands
which should execute quickly.
Making this initialization lazy would be nice.
Would you accept a PR for this?

—
Reply to this email directly or view it on GitHub
#101 (comment).

@bronze1man
Copy link
Author
bronze1man commented Jun 14, 2018 •
edited
Loading

This bug make my vps out of memory with the data race build today.
I have to change it to manual and lazy init 3 years later...

@bronze1man bronze1man mentioned this issue Jun 14, 2018
Closed
@bronze1man bronze1man mentioned this issue Aug 16, 2018
Open
@bronze1man bronze1man reopened this Aug 16, 2018
@kevin-matthew kevin-matthew mentioned this issue Jan 15, 2021
Closed
@gtt1995 gtt1995 mentioned this issue Mar 29, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bronze1man @gconnell @hlandau
0