[BGPCEP-380] BGP ingestion in Beryllium is too slow Created: 29/Jan/16  Updated: 03/Mar/19  Resolved: 05/Feb/16

Status: Resolved
Project: bgpcep
Component/s: BGP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Vratko Polak Assignee: Milos Fabian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5139

 Description   

While ingesting 1 million one-prefix BGP update messages takse 2-3 minutes with Lithium snapshot [0], corresponding Beryllium snapshot manages to ingest only around 300000 messages in 5 minutes [1].

There is no obvious reason for Beryllium to be slow this much, so this performance regression is a Bug.

[0] https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-only-stable-lithium/92/robot/bgpcep-bgp-ingest.txt/Singlepeer%20Prefixcount/Wait_For_Stable_Talking_Ipv4_Topology/
[1] https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-periodic-bgp-ingest-only-beryllium/88/robot/report/log.html#s1-s2-t5-k2-k2-k7-k29-k1-k6

 Comments   
Comment by Milos Fabian [ 02/Feb/16 ]

The concern was addressed to the controller developers - https://lists.opendaylight.org/pipermail/controller-dev/2016-February/011531.html

Comment by Milos Fabian [ 03/Feb/16 ]

Fixed by: https://git.opendaylight.org/gerrit/#/c/33970/ and https://git.opendaylight.org/gerrit/#/c/33971/

Comment by Radovan Sajben [ 04/Feb/16 ]

Test case reference:
bgpcep_bgp_ingest_txt_singlepeer_changecount_check_listening_ipv4_topology_count
bgpcep_bgp_ingest_txt_singlepeer_changecount_wait_for_stable_ipv4_topology_after_listening

Comment by Radovan Sajben [ 05/Feb/16 ]

Updated test case references:
=============================

bgpcep_bgp_ingest_txt_singlepeer_prefixcount_wait_for_stable_talking_ipv4_topology
bgpcep_bgp_ingest_txt_singlepeer_prefixcount_check_talking_ipv4_topology_count
bgpcep_bgp_ingest_txt_singlepeer_prefixcount_wait_for_stable_listening_ipv4_topology
bgpcep_bgp_ingest_txt_singlepeer_prefixcount_check_listening_ipv4_topology_count

bgpcep_bgp_ingest_txt_singlepeer_changecount_wait_for_stable_talking_ipv4_topology
bgpcep_bgp_ingest_txt_singlepeer_changecount_check_talking_ipv4_topology_count
bgpcep_bgp_ingest_txt_singlepeer_changecount_wait_for_stable_ipv4_topology_after_talking
bgpcep_bgp_ingest_txt_singlepeer_changecount_check_listening_ipv4_topology_count
bgpcep_bgp_ingest_txt_singlepeer_changecount_wait_for_stable_ipv4_topology_after_listening

bgpcep_bgp_ingest_txt_manypeers_prefixcount_wait_for_stable_talking_ipv4_topology
bgpcep_bgp_ingest_txt_manypeers_prefixcount_check_talking_ipv4_topology_count

bgpcep_bgp_ingest_txt_manypeers_changecount_wait_for_stable_talking_ipv4_topology
bgpcep_bgp_ingest_txt_manypeers_changecount_check_talking_ipv4_topology_count
bgpcep_bgp_ingest_txt_manypeers_changecount_wait_for_stable_ipv4_topology_after_talking

Comment by Vratko Polak [ 05/Feb/16 ]

Beryllium run on Sandbox now fails [0] pointing to a search which lists only this Bug. But symptoms are different, the test sees zero prefixes, so a Bug different from this one should be open for that.

[0] https://jenkins.opendaylight.org/sandbox/job/bgpcep-csit-1node-periodic-bgp-ingest-only-beryllium/6/console

Generated at Wed Feb 07 19:12:53 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.