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

'show ip ospf interface' really slow when many interfaces #746

Open
frdaigle opened this issue Apr 5, 2023 · 5 comments · May be fixed by #780
Open

'show ip ospf interface' really slow when many interfaces #746

frdaigle opened this issue Apr 5, 2023 · 5 comments · May be fixed by #780
Assignees

Comments

@frdaigle
Copy link

frdaigle commented Apr 5, 2023

This command will last about 17 minutes on a switch that has 540 ospf interfaces.

Looking at the parser code, a 'show run | section vrf {vrf-id}' is run for each interfaces to gather vrf data. To optimize the code, it would be better to do 'show run | section vrf' once and refer to this returned dictionary for each OSPF interfaces.

@vkuttykr
Copy link

Hi, Ticket heading and problem statement both are different. Could you please clarify whether you are looking for the API for show run | section vrf ?, and for Which OS / Device model ?

And , also would be good if you can share the reference logs (manual) to analyze further data to cross check. Are the system CPU/memory status only peaks when executing these cli`s ?

@sudheergovindu
Copy link

Could you please clarify and share logs to analyze and to cross check, if you are still facing the issue.

@sudheergovindu
Copy link

As we currently not supporting, we will add to backlog for support as per priority of customer need to resolve the issue you are facing in future. If you need further assistance, please let me know and I'll do my best to provide additional guidance.

@sudheergovindu
Copy link

Thank you for bringing this issue to our attention. Unfortunately, at the moment, we do not support the specific request you have made. However, we value your feedback and understand the importance of resolving this issue for our customers. Therefore, we will prioritize adding it to our backlog for future support based on the level of need expressed by our customers.

If you require any further assistance or have any other questions, please don't hesitate to let me know. I am here to help and will endeavor to provide any additional guidance or information you may require.

@virrsa virrsa linked a pull request Aug 18, 2023 that will close this issue
5 tasks
@virrsa
Copy link
Contributor

virrsa commented Aug 18, 2023

Opened PR #780 to address this issue. The optimized parser brought a 17 minute run of the command down to ~2 minutes.

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

Successfully merging a pull request may close this issue.

4 participants