Jump to content
Dante Unbound: Share Bug Reports and Feedback Here! ×

Warframe Stress-Test Easter-Egg


[DE]Glen
 Share

Recommended Posts

3-9-2017: Warframe Stress Testing

Rig:

Intel Core i7-6700k (4.0GHz, all stock clocks)
32 GB RAM (2400 MHz)
Nvidia GeForce MSI GTX 1080 (stock clocks except for Core Clock)

Each two tests elapsed for 10 minutes. Each test was a fresh-start test.

 

WF TEST #1 (Nvidia Driver Version 378.78) – all options on, 1600x900 windowed)

Starting RAM (in-game heap): 512MB
Starting RAM (Task Manager): 1202MB  

Ending RAM (In-game heap) 524MB
Ending RAM (Task Manager) ~2100MB   -- 900 MB spread would’ve gotten bigger if left running.

WF TEST #2 (Nvidia Driver Version 378.78) – PhysX disabled, 1600x900 windowed)

Starting RAM (in-game heap): 480 MB
Starting RAM (Task Manager): 1090 MB

Ending RAM (in-game heap): 530 MB
Ending RAM (Task Manager): 1103 MB

 

--

So even with Nvidia’s newest Game-Ready Driver, it seems that PhysX is still a major culprit to the overall resource usage in Warframe. I’m going to start testing with Overlays on/off, in combination with PhysX soon.

This is all the time I got for now.

(My brother and I have been using Driver Version 375.95 for a while, and have received no issues related to memory leaking. I'm not sure where the problem started, but from what I've seen, it is not related to your hardware. It is indeed a driver problem.)

Edited by AEP8FlyBoy
Link to comment
Share on other sites

For science :)
(I turned on Nvidia Physics)

Also before I updated my Nvidia driver I did get a Windows warning after then I turned off the Nvidia Physics and it worked fine.
(Glen if you have a chance can you revert my dojo decoration builds since then we can not use our dojo like 400+ decorations)

 

Edited by PETI258
Link to comment
Share on other sites

7 hours ago, SprinKah said:

I want a room to do all this stuff!

SPawn enemies to fight each other for fun!

a Battle simulator....I want this...I really want this...to pass the time.

 

also...sorry I don't really understand everything else.

you mean the simulacrum?

Link to comment
Share on other sites

Just now, Fylas said:

you mean the simulacrum?

Simulacrum too limited, can only spawn 20 enemies

the terrain is boring too...plus you can't really direct specific enemies from specific factions to make it cool.

 

and yes, I know, Simulacrum is the closest thing we have currently to that...but we need more!

Link to comment
Share on other sites

Wow I didn't know phys x is bleeding THAT much, this stays off when I'm not recording X_X  

2 tests, 30 minutes each, first with second without physx. both clean start ups. 

Client data :

Windowed full screen. 

Direct x 10, 11 , 64 bit mode, bulk download, aggressive download, multi-threading rendering and launcher GPU acceleration enabled.

Launcher version :

2017.03.06. 11.03 

Engine Version :

2017.03.09 14.45

Pc data :

windows 10. newest driver version.  12gb of ram (I love unusual amounts leave me alone) with a gtx 970 and a i7 2600k 

Driver versions, cpu gpu etc. 

 

Spoiler

 

5T84W8Z.jpg

 

Test 1, phys x on 30 minutes start and end

Spoiler

OevOBbG.jpg

WjbfUqp.jpg

 

 

Test 2, phys x on 30 minutes start and end

Spoiler

fxbpVel.jpg

B5Wuzvk.jpg

 

 

Link to comment
Share on other sites


2017-Mar-10

Intel Core i7-6700K (4 GHz, Stock)
16 GB RAM (2666 MHz)
EVGA GeForce GTX 980 FTW (4GB VRAM, factory-overclocked)
Nvidia Driver Version 378.78
Windows 10 Professional x64 Version 1607 14393.693

10 Minute run of "corpus.outbreak" - Warframe all options on except motion blur, 1920x1080 fullscreen, PhysX on

Start RAM (in-game heap): 485 MB
Start RAM (Commit): 1.7 GB
Start RAM (Working Set): 1.3 GB  

End RAM (In-game heap) 520 MB
End RAM (Commit): 3.1 GB
End RAM (Working Set): 2.6 GB 

I only had to run it for 10 minutes to already have more than doubled the needed RAM.
During Pacifism Event I used to exhaust my 16 GB RAM in about 1 hour, image below.
(Please note that I did the run above with everything else closed, including any overlays or recording softwares - no change happened tho).

Disabling PhysX in Warframe instantly fixed the leak.

bnoUe9T.png

Edited by EWar
changed image host
Link to comment
Share on other sites

My commit size gets smaller, is that normal?

It starts off the same as everybody else's ~1.2GB, it rises initially to ~1.4GB, then after a long period drops down to >1GB. For example:

warframeramdiscord2vvjke.png

I am using Driver version: 376.53 - Which were apparently pushed through by Microsoft. 

EDIT1:

PC config:

CPU: AMD 8320 4.5GHz OC
GPU: EVGA GTX 970 SC
PhysX: MSI GTX 660 [Not used for testing, though used for normal play]
RAM: 8GB Mushikin something
SSD: Samsung Evo 256GB
Drivers: 376.53 [Posted above]

EDIT2:

@[DE]Glen This may be a little interesting, updated from 376.53 to 378.78 [latest drivers at time of posting], instant memory leak:

Spoiler

Start:

newdriversstart79j75.png

End:

newdriversendz1kxl.png

However, actually using my GTX 660 for its intended purpose gives no memory leak [still on 378.78]:

Spoiler

Start:

newdriversstart20dkga.png

End:

newdriversend2u9jki.png

I have run both the above tests twice, back to back. When physX is running on a dedicated PhysX card i have no issues. I'm currently running a third test as i type this and the 970 is causing a leak, when designated PhysX work - Currently sitting at 2GB and counting.

Edited by MillbrookWest
Link to comment
Share on other sites

Hi @[DE]Glen

I hope this helps:

Two monitors setup (1920x1080 on this one I run game fullscreen, 1366x768 for Mozilla, Task Manager and stuff).

Win 7 64 bit

nVidia drivers: 378.78

AMD FX 8350 black edition 8 CPUs ~4.0 GHz

DirectX 11 (hate Win 10 so I won't get 12 in the near future)

nVidia GeForce GTX 960 G1 Gaming 4GB GDDR5 (a potato card with 128 bit and 1266 MHz :()

16 GB RAM DDR3 1600 MHz

 

First run normal game:

FPS: 60

RAM: 591 MB

Commit: 1 523 128 K

Corpus.Outbreak (initial start):

FPS: 60

RAM: 500 MB

Commit: 1 450 536 K

Corpus.Outbreak (30 minutes):

FPS: 58-60

RAM: 550 MB

Commit: 3 811 384 K

Corpus.Outbreak (1 hour):

FPS: 58-60

RAM: 560 MB

Commit: 6 853 020 K

 

When I checked after hour my overall memory usage was over 10 GB this was the first time It got so high.

 

 

 

Link to comment
Share on other sites

Gonna post this too because I got memory leak issues recently.

 

PC setup:

i7 4770

Gigabyte Z97X

32GB RAM

Nvidia GTX980Ti + Driver ver 378.49

Win7 64bit

2 monitors, (2560x1440 for the main and gaming, another one is 1920x1080 drawing tablet)

 

Tried corpus.outbreak, and here's some results (I run on borderless fullscreen mode, PhysX always on):

Initial:

In game RAM: ~500MB

Commit: ~1200MB

1 hour run:

In game RAM: ~800MB

Commit: ~8000MB

 

Pardon me I didn't recorded the precise numbers, but yes, the commit keeps growing while in game stays on ~800MB.

Will report back after I update my nvidia driver. Some friends also told me to optimize via the launcher, tried that and still have memory leak btw.

Link to comment
Share on other sites

40 minutes ago, Kampidh said:

Gonna post this too because I got memory leak issues recently.

 

PC setup:

i7 4770

Gigabyte Z97X

32GB RAM

Nvidia GTX980Ti + Driver ver 378.49

Win7 64bit

2 monitors, (2560x1440 for the main and gaming, another one is 1920x1080 drawing tablet)

 

Tried corpus.outbreak, and here's some results (I run on borderless fullscreen mode, PhysX always on):

Initial:

In game RAM: ~500MB

Commit: ~1200MB

1 hour run:

In game RAM: ~800MB

Commit: ~8000MB

 

Pardon me I didn't recorded the precise numbers, but yes, the commit keeps growing while in game stays on ~800MB.

Will report back after I update my nvidia driver. Some friends also told me to optimize via the launcher, tried that and still have memory leak btw.

so far it looks like it's a issue with phys X turn it off, and restart the game, no problem anymore :O at least with the newest drivers

Link to comment
Share on other sites

3 hours ago, Fylas said:

so far it looks like it's a issue with phys X turn it off, and restart the game, no problem anymore :O at least with the newest drivers

Haven't tried driver update yet, but yeah, it seems to work. I've tried turned off the PhysX and tried to run again for 2 hours.

The commit size stays at ~1900MB

Link to comment
Share on other sites

I cant even run the stress test. the leak is so bad, that it takes 5 minutes for the control+alt+del function to bring up the options to OPEN task manager, another 5 for it to actually show up on screen.... at that point. it crashes. what i can tell you is it starts around the 500 mark, and ends around 3k when i log off

Link to comment
Share on other sites

2 hours ago, Moysa said:

I cant even run the stress test. the leak is so bad, that it takes 5 minutes for the control+alt+del function to bring up the options to OPEN task manager, another 5 for it to actually show up on screen.... at that point. it crashes. what i can tell you is it starts around the 500 mark, and ends around 3k when i log off

have you disabled physx? what are your specs/ driver versions ingame settings etc etc? 

Link to comment
Share on other sites

Don't know how much I'd help (I don't even remember my VGA) but here's my stats:

Normal Login: 60fps, Time 16.7ms 645MB RAM

Special Login Reference: 60fps, Time 16.7ms 498MB RAM Task Manager: 31.2% CPU, 1.016,7MB RAM

Special Login 30m: 55fps, Time 23.3ms, 533MB RAM  Task Manager: 38.6% CPU, 1024.3MB RAM

Link to comment
Share on other sites

GTX 980
Version 378.78

PhysX is clearly leaking. Turning it off gives no leak.

 

This explains why the last Event (pacifism defect) killed my rig. Game crashed after telling me that i dont have enough RAM (i have 16gb)

Edited by ButterLutter
Link to comment
Share on other sites

Every 378.xx driver up to the latest 378.78 leaks in combination with Warframe and PhysX enabled. Downgrade to 376.xx and the leak is gone. Strange thing though is that both driver branches use the same PhysX system software version 9.16.0318.

Link to comment
Share on other sites

I will contribute with my rather old AMD rig.

Test date: 12.03.2017

 

Specs

CPU: AMD Phenom II X4 955 Black Edition (overclocked to 3,8 GHz)

GPU: AMD Radeon HD 7850 (2 GB VRAM)

RAM: 8 GB DDR3 (@669MHz)

MB: GA-88GMA-UD2H (AMD 880G)

Graphics Driver: Crimson ReLive 17.3.1

OS Version: Windows 10 Pro (Build 14393)

 

Results

@ start:

Ingame: 490 MB // Task Manager: 930 MB

@ 20 minutes:

Ingame: 515 MB // Task Manager: 920 MB

@ 40 minutes:

Ingame: 520 MB // Task Manager: 925 MB

@ 60 minutes:

Ingame: 520 MB // Task Manager: 925 MB

 

No problems here I guess! :clap:

Link to comment
Share on other sites

SPECS

I5-2310

12 GB RAM

GTX 570 4GB, latest drivers installed

 

did two 20min runs plus the corpus outbreak, on all cases:

STARTING DATA

HEAP: ~620 Mb RAM

TASK MANAGER: ~1,3 Gb RAM

FPS: well over 60 fps

 

ENDING DATA

HEAP: ~840 Mb RAM

TASK MANAGER: ~1,6Gb RAM

FPS: hovering around 64, dipping into 50 at times

Settings are a mid-high, no physx

 

 

My guess is that I have HEAP issues? If so help and whatnot.

Edited by Kriegsherr
Link to comment
Share on other sites

19 hours ago, Kriegsherr said:

My guess is that I have HEAP issues? If so help and whatnot.

Hard to tell from such a short run -- but that said I think there's a small leak with the Juggernaut's spikes that I should look into one day.

Link to comment
Share on other sites

Ok I think we have enough data from the latest drivers, thanks. If you're willing to try something older than 378.48 and newer than 376.53 we might be able to box it in for Nvidia:

378.78 on everything leaks

378.66 on GTX 950 leaks

378.48 on GTX 980Ti SLI or GTX 1080 leaks 

... ? ...

376.53 on GTX 970 does not leak

375.95 on GTX 1080 does not leak

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...