Thanks, Prakash - I see there is a good build now... in case you are still around. -Kathy
On Thu, 2010-03-25 at 01:54 -0500, Prakash PM (JIRA) wrote: > [ > http://track.sipfoundry.org/browse/XX-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49461#action_49461 > ] > > Prakash PM commented on XX-6619: > -------------------------------- > > Bob, The 'Type' in 'RAID Properties' of my SAS Adapter - SAS1068E is "RAID 1 > (IM)" and the Status is 'Optimal'. So, I believe the RAID configuration is > working fine. > > Kathy, I have fixed the errors that you pointed. I don't have the build with > r18415 today (It is r18410). I will start the test tomorrow with DEBUG > logging after I get this build. > > Thanks, > Prakash > > > Memory usage of sipXproxy increases and the SUT swaps memory during soak > > testing. > > --------------------------------------------------------------------------------- > > > > Key: XX-6619 > > URL: http://track.sipfoundry.org/browse/XX-6619 > > Project: sipXecs > > Issue Type: Bug > > Components: sipXproxy > > Affects Versions: 4.1 > > Environment: sipxproxy 4.1.0-016475 2009-09-15T22:49:30 oem-centos5 > > Dell R-300 with 4GB RAM and 6GB Swap Area. > > Reporter: Prakash PM > > Assignee: Prakash PM > > Priority: Critical > > Fix For: 4.1.7 > > > > Attachments: 15_Mar-valgrind-test.zip, 17_Mar-valgrind-Report.zip, > > 19_Mar-valgrind.zip, Distributed_Soak_Test_Snapshot_without_logs.tar.gz, > > Mar19_DistribGraphs.zip, Mar19_MasterGraphs.zip, > > Mar_19_Distributed_Snapshot_after_valgrind_test_at_NOTICE_level_logging.tar.gz, > > Mar_19_Master_Snapshot_after_valgrind_test_at_NOTICE_level_logging.tar.gz, > > Master_Soak_Test_Snapshot_without_logs.tar.gz, > > memMon_reports_of_72_Hour_HA_Comm_Soak_Test_at_NOTICE_level_logging.zip, > > valgrind-report.txt, valgrind-report_DISTRIBUTED.txt, > > valgrind-report_MASTER.txt > > > > > > During 72 hour Comm Soak/Media Soak Test, memory usage of sipXproxy was > > uniform at 20% till 32nd hour. After 32 hours ((sunday, 4AM)) it started > > increasing and at the end of the test it was at 57%. The SUT started > > swapping memory in the 50th hour and it was 30% at the end of the test. > > The test completed with 99.9% results. But the SUBSCRIBE test was failing > > with '408 Request Timeout' from 48th hour, recovered in the 57th hour. > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
