PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001044PacketFenceperformancepublic2010-08-09 00:052015-02-13 15:35
Reporterobilodeau 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001044: pfsetvlan is memory hungry (217Mb on a normal, inactive setup)
DescriptionThere is definitely something grossly inefficient in there. A little run in the debuger could give us a clue.
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                    
 
2760 root      15   0  480m 217m 1104 S  0.0 43.3   0:02.45 pfsetvlan
Steps To Reproduce1. Start packetfence
2. Wooaaa pfsetvlan is taking all that memory!?
3. Profit
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-08-09 00:05obilodeauNew Issue
2010-08-09 00:05obilodeauStatusnew => assigned
2010-08-09 00:05obilodeauAssigned To => obilodeau
2010-08-09 16:50obilodeauNote Added: 0001628
2010-09-15 11:23obilodeauTarget Version1.9.1 => 1.9.2
2010-09-22 16:02obilodeauTarget Version1.9.2 => 1.9.3
2012-10-19 15:06fgaudreaultAssigned Toobilodeau =>
2012-10-19 15:06fgaudreaultTarget Version1.9.3 => general
2015-02-13 15:35lmunroNote Added: 0003739
2015-02-13 15:35lmunroStatusassigned => closed

Notes
(0001628)
obilodeau   
2010-08-09 16:50   
for fun I did a simple test:
ran pfsetvlan in the debuger normally breaking right before the main loop

with 20 trap handler and 5 trap parser
memory usage: 389Mb

with 1 trap handler and 1 trap parser
memory usage: 53Mb

No work at all was performed this means that there is a memory sharing opportunity here! We are probably spawning the threads too early?
(0003739)
lmunro   
2015-02-13 15:35   
No longer relevant.