selenium webdriver - Protractor tests slowing down when runtime increases -

i have set of protractor tests in 1 suite require 45 minutes 1 hours complete. tests progress, notice severe increase in run time per test.

the following code tests i'm executing in spec.js file:

for (var = 0; < users.length; i++){     (function(test){          it('should load team page', function(){             teampage.loadteampage();         });         it('should create credential team', function(){             teampage.createcredentialwithteam(test, 'test team');         });         it('should create schedule team', function(){             teampage.createschedulewithteam(test, 'test team');         });         it('should create task team', function(){             teampage.createtaskwithteam(test, 'test team');         });         it('should edit team', function(){             teampage.editteambyname(test, 'test team', 'new test team','testing department', true);         });         it('should add team member', function(){             teampage.addteammember(test, 'test team', 'foo', 'admin', true);         });         it('should load department page', function(){             departmentpage.loaddepartmentpage();         });         it('should edit department', function(){             departmentpage.editdepartmentbyname(test, 'testing department', 'testing department edited', 'non', true);         });         it('should view department', function(){             departmentpage.viewdepartmentbyname('testing department')         });         it('should add departmentmember', function(){             departmentpage.adddepartmentmember(test, 'testing department', 'foo', 'admin', true);         });         it('should load organisation page', function(){             organisationpage.loadorganisationpage();         });         it('should add department', function(){             organisationpage.adddepartment(test, 'test department protractor', 'test case organisation', true, true);         });         it('should attempt add members organisation', function(){             organisationpage.addorganisationmember(test, 'test case organisation', 'foo', 'admin', true);         });         it('should check organisation , compare details view page', function(){             organisationpage.vieworganisationbyname('test case organisation');         });         it('should try edit organisations details', function(){             organisationpage.editorganisation(test, 'test case organisation', 'edited test case organisation');         });         it('should log out', function(){             homepage.logout();         });     })(users[i]); } 

i'm not sure if bad practice write of inside for-loop can't imagine if has drop in performance. starting out, every test within for-loop takes 15-20 seconds. when testing entire loop, i've encountered spec time-outs forced me adding following code conf.js:

jasminenodeopts: {defaulttimeoutinterval: 60000} 

this increases default time out value of 30000(ms) 60000(ms). speed @ protractor interacts browser visually decreasing. i've read starting new instance of webdriver before each test seems overall increase in runtime.

edit: following crossed mind: have html-screenshot-reporter jasmine2 attached process captures screenshot after every test, possible caches every single 1 of these images , accumulates tests put strain on host system?

has encountered similar issue protractor? input appreciate. if require more information, don't hesitate ask.

cheers