Puget Systems print logo

https://www.pugetsystems.com

Read this article at https://www.pugetsystems.com/guides/1287
Article Thumbnail

Puget Systems Adobe After Effects CC Benchmark

Written on December 5, 2018 by Matt Bach
Share:

At Puget Systems, one of our primary goals is to make sure that our customers end up with a fast, reliable workstation that is perfectly tailored to their unique workflow. The main way we do this is by benchmarking a wide range of hardware in After Effects (and numerous other software packages) that we then publish in our ongoing series of hardware articles.

However, while this ensures we are selling the right hardware, it does not give our customers a great idea of how much faster a new workstation would be compared to their existing system. To address this issue, we are making our internal Ae benchmark available for public download so that anyone can compare their own computer to our latest After Effects hardware articles. Even better, this benchmark is compatible with both Windows and Mac-based systems!

Download
Puget Systems After Effects CC 2019 Benchmark
(BETA ver 18.12.18)

We also have a benchmark available for Adobe Photoshop CC

How to run the benchmark

After downloading the benchmark, unzip it to a convenient location - we recommend placing it on the same drive that you store your active projects as there are a few media assets used throughout the benchmark. Next, simply open the "PugetBenchmark.aep" project file and follow the instructions shown in the "Benchmark Instructions" composition.

Note that while a number of settings will be automatically set by the benchmark script, there are three that you will need to set manually as they cannot be effectively scripted. These settings are:

  • Enable "Allow Scripts to Write Files and Access Network" in "Edit -> Preferences -> General"
  • Disable "Disk Cache" in "Edit -> Preferences -> Media & Disk Cache" (having disk cache enabled results in inconsistent results as Ae is not fully consistent on when it will write files to the cache)
  • Set Spacebar Preview to "Play Once" in the Preview Window

Once the benchmark is completed, we recommend reverting these back to their original settings since things like Disk Cache are probably something you want to have enabled.

With After Effects configured, you can run the "PugetBenchmark.jsxbin" script by going to "File -> Scripts -> Run Script File" and browsing to the benchmark folder. If you do not see this script, make sure the open dialog is not restricted to only showing ".jsx" files. You will need to confirm one prompt to clear your existing disk cache, then the benchmark will proceed. Most systems should be able to complete the benchmark in 30-60 minutes, although it will vary based on the performance of your system.

When the benchmark is complete, it will give you an "Overall Score" as well as individual scores for the different types of tests. A log file is generated in the benchmark folder that includes these scores as well as the time in seconds it took to complete each individual task. You can compare your scores to those in our After Effects hardware articles dated from December 2018 and newer.

Compatibility

This benchmark is designed for After Effects 2019 and should run on virtually any Windows or Mac-based system that has After Effects CC 2019 installed. However, due to the size of the test projects it is ideal to have 16GB or more of system RAM and a GPU with 4GB+ of VRAM.

Note that this benchmark is still in BETA. Plug-ins and customized preferences in particular may prevent the benchmark from running properly. If you run into any issues, we recommend resetting your preferences to default - be sure to make a backup first!

Benchmark tests and projects

Our benchmark tests RAM Preview FPS (in both half and full resolution), FPS when rendering a composition out to a file, and performance when doing a warp stabilize and 3D camera tracker analysis.

Many of our benchmarks are based around the excellent tutorials provided by VIDEO COPILOT. If you wish to understand what is going on in those compositions, we highly recommend watching the following tutorials:

How does the scoring work?

The scoring system used in our benchmark is based on the performance relative to a reference system with the following specifications:

  • Intel Core i9 9900K 8 Core
  • NVIDIA GeForce RTX 2080 8GB
  • 64GB of RAM
  • Samsung 960 Pro 1TB
  • Windows 10
  • Adobe After Effects CC 2019 (ver. 16.0.0)
  • Overall Score: 1000
  • Standard Score: 100
  • C4D Score: 100
  • Tracking Score: 100

The Tracking Score is the average of the scores for warp stabilize and 3D camera tracker tests. The C4D Score includes the average of RAM Preview (half and full res) and Final Render results for the compositions that utilize the Cinema 4D 3D renderer. Likewise, the Standard Score is the average of the RAM Preview (half and full res) and Final Render results for the compositions that do not use the C4D renderer.

The Overall Score is based on a weighted average of the three types of tests based on what our customers tend to be the most concerned about:

  • Standard Score - 50%
  • C4D Score - 25%
  • Tracking Score - 25%

Commercial use & pricing

Our After Effects benchmark is provided completely free of charge for anyone to download and use. We only ask that if you are using it for commercial purposes that credit "Puget Systems" (please do not shorten to "Puget") and provide a link to this page. Examples:

  • Web: After Effects benchmark provided by workstation manufacturer Puget Systems
  • Print: Puget Systems After Effects benchmark can be downloaded at www.pugetsystems.com/go/PSBenchmark

Update Log

Version 18.12.18

  • Minor bug fix

Version 18.12.17

  • Added more robust detection for when the benchmark starts/stops RAM Preview and Render testing. This is to fix a bug on some systems where if the test doesn't start within a few seconds, the benchmark thinks it already finished.

Version 18.12.10

  • Added Ae version check to make sure Ae 2019 (ver 16.x) is being used.
  • Initial benchmark errors (Disk Cache not disabled, Ae not using English, Ae version mismatch, etc) now allow for you to continue the benchmark anyways - although the benchmark will probably break so that isn't recommended.

Version 18.12.0

  • First release.
Tags: After Effects, Benchmark, Public
ComputahNerd

Hi! thanks a lot for this! But, I tried to set preview to loop once, but the script still wont start and says I need to set preview to "loop once". Despite having restarted AE and even rebooted the machine and previews actually only playing once when testing. Any ideas?

Posted on 2018-12-06 06:47:13

Huh, interesting. Are you on Mac or PC? And you sure you are setting it for spacebar and not any of the other preview hot keys? That setting is a little bit weird in the setting files, so I'm worried there might be something weird with it. I'll take a look at it later to see if there is something I missed and worst case I'll swap it over to a warning rather than a hard error that stops the benchmark from being run.

Posted on 2018-12-06 06:55:57
ComputahNerd

Hey, yeah I'm on a PC. I have tried to restart AE many times and also tried to change all the other playback settings (range and play from) - It refuse to start. See screenshot: http://prntscr.com/lrcx82

Posted on 2018-12-06 06:59:02

Yea, looks like a bug then. I can't check it right now (and unfortunately I might not be able to tomorrow either), but when I can I'll check it and release an update. My guess is just that the script isn't finding that one setting since I actually have to do a file text search to get it and there is probably some weirdness going on.

Thanks for pointing out the bug!

Posted on 2018-12-06 07:08:06
ComputahNerd

Thank you - looking forward to test :) I was just curious as to how my threadripper 1950x performed - which I expect is quite low - as I noticed the slower responsiveness of the entire program after getting this CPU. Though based on your charts, even the 2950x scores pretty bad compared to Intel CPUs - proving that AMD threadripper series is a pretty bad investment for any AE users.

Posted on 2018-12-06 07:26:15

I couldn't find anything wrong, the only other thing I can think of is that if you aren't use Ae 2019 (ver 16.x) it wouldn't be able to detect that you changed that setting since the setting file wouldn't exist.

I just added a Ae version check to the script, but also made it so those errors are more of a warning. You can have it run the benchmark anyway, but it just means that it might break at some point or get stuck. So re-download it and give it a try.

Posted on 2018-12-10 21:40:28
ComputahNerd

thanks will test it. I use the very latest version of CC 2019 AE.

Posted on 2018-12-10 21:48:36
ComputahNerd

So even though it gave me the same warning now and also another which was called "unknown" it worked fine. It wen't through all the benchmarkings. It said also that it couldnt perform the changes, though I had set it up myself. (perhaps I should have started AE in administrator mode?)

Anyway, results for my 1950x was rather bad, as anticipated, but it was good to see that the experience I have had with the CPU made sense according to the test.
Overall:634 - standard:66 - C4D: 58 - Tracking: 63

Almost as bad as Mac Pro, So awful results both in standard and C4D scenes, which you guys have stated before. TR4 is by no means a good overall CPU for creators, except only those who need many cores for rendering for a cheap buck.

Posted on 2018-12-11 12:18:18
Hugo Scali

Hi, I wanted to ask permission to use the results of their benchmarks on my Spanish-language YouTube channel since I plan to make a video about the workstation. Since it is not true that always more nucleos is the best choice and the choice of components should be based on the determined task that they are going to execute. Obviously I will put in the description that the data was extracted and analyzed from pugetsystem and I will leave the link to the site.

This is my channel: https://www.youtube.com/cha...

Posted on 2018-12-09 08:15:59

Sure! We would appreciate having some reference to "Puget System's After Effects CC Benchmark" (or something along those lines) on the graphic itself in addition to a link in the description, but absolutely you can use results from our benchmark.

Posted on 2018-12-10 18:13:50
mateo5

Thanks for this!! it's really helpful :) Something that would make this more awesome IMHO is to include in the downloads the benchLog csv of scoring machine, in order to be able to compare in detail each one of the tests with the base config that sets the benchmark score. I for one, would love to see how many fps the base machine got in the polygon test RAM preview in order to compare to mine. In the polygon test I got: RAM Preview (Half Res.),Polygon Project,11.1,FPS.

Posted on 2018-12-08 12:02:58

The main reason we didn't get too much into the reference scores is because that score is not going to change over time. So as there are driver updates, Windows updates, Ae updates, etc. the actual performance of a system with a i9 9900K is going to change more and more from the reference score. What I would do is to compare your results to those in out hardware articles. https://www.pugetsystems.co... right now is the only article using this exact benchmark, but it includes results for CPUs like the i9 9900K.

Posted on 2018-12-10 18:11:11
Craig Marshall

Thanks for this tool! But I'm confused by the results on our systems. Our benchmarks are way above the "top" score. Most of our systems are showing an overall score of 6100 or more. Other metrics are equally out of range (Standard score: 798, C4D: 804, etc). Any idea what I'm missing here?

Posted on 2018-12-12 22:04:47

Huh, that is interesting. Could you grab the log file (labeled BenchLog_XXXXXX.csv in the benchmark script folder) and toss it to me in an email at labs@pugetsystems.com ? Those scores look like they are just multiplied by 10, but I can't think of how that could be possible. The other thing it could be is that either the disk cache isn't being cleared (if you have run the benchmark multiple times) or the viewport resolution isn't getting properly set to half/full. Seeing the log file will let me determine if it is a score calculation issue or something wrong with the actual run.

The other thing you could try is to reset your Ae Preferences. You can just make a copy of the preference folder, then go back to it after you run the benchmark if you don't want to lose any of your custom preferences: https://helpx.adobe.com/aft...

Edit: Actually, include the StatusLog_____.txt file as well if you can.

Posted on 2018-12-12 22:55:29

Hey Craig, I just sent you an email, but for anyone else who had this issue it should be fixed in the 18.12.17 version I just uploaded. I think the issue was that on some systems, it takes longer to start the render than I expected. That means that sometimes the benchmark would think that the render was done before it actually even started. I added some extra code to help make sure that doesn't happen so hopefully it should work for you now!

Posted on 2018-12-17 23:55:35
CPH

Hi,

First, thanks for the help so far … am trying to diagnose why my new Radeon RX580 makes no difference in AE rendering time (in 'Mercury GPU Acceleration - Metal' or '...OpenGL', versus '...Software Only'). Was about to run the Puget Sound Benchmark but the last step has 'PugetBenchmark.jsxbin' grayed-out (see attachment):
https://uploads.disquscdn.c...

This page was very helpful in trying to understand these issues –– https://www.pugetsystems.co... –– *I'm only interested in Standard Render speeds btw*, for what I do.

I can return the card if nec. But am wary of NVIDIA in Macs, due to potential hassles and learning curves, and also cost is a factor.

System:
Razer Core X - Thunderbolt 3 eGPU
Radeon RX 580 8GB card
MacBook Pro (13-inch, 2017, Thunderbolt 3 ports, 2.3 GHz Intel Core i5, 16GB RAM, Mojave 10.14.2)
Primary software: After Effects/Premiere/CC2019)
Output drive: Samsung Portable SSD T5

~

Have re-started AE btw. Also, the Activity Monitor/GPU History window shows the rendering is being done by the Radeon card.

Posted on 2018-12-15 15:51:36
CPH

Hi,

First, thanks for the help so far … am trying to diagnose why my new Radeon RX580 makes no difference in AE rendering time (in 'Mercury GPU Acceleration - Metal' or '...OpenGL', versus '...Software Only'). Was about to run the Puget Sound Benchmark but the last step has 'PugetBenchmark.jsxbin' grayed-out (see attachment).

This page was very helpful in trying to understand these issues –– https://www.pugetsystems.co... –– *I'm only interested in Standard Render speeds btw*, for what I do.

I can return the card if nec. But am wary of NVIDIA in Macs, due to potential hassles and learning curves, and also cost is a factor.

System:
Razer Core X - Thunderbolt 3 eGPU
Radeon RX 580 8GB card
MacBook Pro (13-inch, 2017, Thunderbolt 3 ports, 2.3 GHz Intel Core i5, 16GB RAM, Mojave 10.14.2)
Primary software: After Effects/Premiere/CC2019)
Output drive: Samsung Portable SSD T5

~

Have re-started AE btw. Also, the Activity Monitor/GPU History window shows the rendering is being done by the Radeon card.

~

https://uploads.disquscdn.c...

Posted on 2018-12-16 00:43:04

Are you sure you are trying to run a script and not trying to open a project in Ae? That is the only reason I can think of why that would be grayed out like that. "File > Scripts > Run Script File". If that isn't it, I don't know what else it could be. I would try resetting your preferences and if necessary, uninstall and reinstall After Effects. After that, you should contact Adobe support since not being able to run a script indicates that there is something wrong with either your system or After Effects.

Posted on 2018-12-17 17:40:16
CPH

Thanks very much for your reply Matt … I've found the following solution:

––after selecting "File > Scripts > Run Script File", the resulting window has a pulldown menu at the bottom, with "Enable: Adobe JavaScript file" pre-selected
––but when I select "Enable: Adobe JavaScript binary file" instead, "PugetBenchmark.jsxbin" becomes newly available (is no longer grayed-out). I can then run the test successfully.

Unfortunately, I'm traveling until Boxing Day, and so I'm away from my EGPU+. I'll run the rest of my tests after I'm back, and will be in touch again after that.

Have a good holiday.

Posted on 2018-12-19 02:16:54
CPH

https://uploads.disquscdn.c...

Posted on 2018-12-19 02:18:19
Savage

Hi trying to set up this benchmark and I get a popup immediately on running script that says Puget Systems After Effects Benchmark Complete Overall Score infinity Standard Score infinity C4D Score infinity Tracking Score 0. Clearly it's not running what should I check for?

Posted on 2018-12-18 13:39:35

Oops, that was my mistake when I did the last update. There is a new version that should fix that issue. Sorry about that!

Posted on 2018-12-18 17:18:35
Savage

Thanks Matt that did it!

Posted on 2018-12-18 23:53:05
Jeff

tried the test on the latest version of AE and it just kept looping through the test even though loop playback was off in the Ram Preview UI. Restarted several times with the same result. It did however write out a log and it looks like one time through the test took about 12 minutes. Wondering how that stacks up.

Posted on 2018-12-22 00:34:07

You sure loop is disabled for spacebar preview specifically? If it is, does it continue to loop anyways of you open a comp and manually hit spacebar? Only other thing I can think of is that somehow your "default" playback method is set to something besides spacebar, but I don't know how that could be done.

I would try resetting your preferences to default if you still can't get it to work right.

Posted on 2018-12-22 00:37:04
Enrico Geromin

This is very nice! Thank you for sharing yours develop & research softwares with us!
Will be very cool if in future there will be a Premiere version of this Benchmark. Thanks again for your work ppl!
My old 4930K @4.4ghz scored 539pts!

Posted on 2018-12-24 00:24:37

We have an internal benchmark for Premiere Pro, but it is likely going to be a while before we can make it public. Premiere doesn't have nearly the scripting capability that Ae or Ps have which means we have to use external utilities pretty much exclusively. That is completely fine for us, but it makes it finicky if you don't have the same screen resolution, DPI, workspace, etc. that it is designed for.

Working on it though!

Posted on 2019-01-02 19:54:14
Karl-Jason Mawdsley

Hey - just a score back of infinity for everything except tracking? Running on a Mac

Posted on 2019-01-02 13:16:52

Are you using the latest benchmark version (18.12.18)? There was a bug in earlier versions that caused that problem, but it should have been fixed in the latest.

Posted on 2019-01-02 19:52:20
Karl-Jason Mawdsley

Yeah I just downloaded it from the link above today. I had a few issues with it at first because I'm running Mojave so had to give MagnifytoFit and SendEnter access to control the computer in System Preferences. I'll try and run it again today and get back to you

Posted on 2019-01-03 08:59:37

I just downloaded the benchmark to the iMac Pro we have here and ran it to check it out. I didn't get any errors or any other issues, so my guess is that your problem is related to the Mojave security stuff. You might check out our video to make sure you have everything set properly there: https://youtu.be/mU3j0AM_fPM

After that, it may be a preference setting you have that is messing something up. You could try resetting the preferences to default to see if that fixes it: https://helpx.adobe.com/aft...

https://uploads.disquscdn.c...

Posted on 2019-01-03 18:55:00
Karl-Jason Mawdsley

When I ran it again it seemed to work fine

Posted on 2019-01-04 13:07:20

We typically see a variance of 3-5% between runs, but I don't think seeing a bit more than that across multiple machines would be too unusual. Especially since different systems might have difference applications running in the background, slightly different software configurations, etc., that can all affect benchmark performance.

Posted on 2019-01-07 18:25:52
Steve E Miller

I did this just for fun on my Lenovo Legion laptop that I got about 1.5 years ago. i7-7700HQ 2.8GHz, 16Gb ram. Took more than an hour to run it.
Results aren't too bad compared to the reference system considerinng the hardware differences.
Overall: 498.25
Standard: 55.6
C4D: 40.5
Tracking:: 47.6

Posted on 2019-01-07 19:32:06
RogueScholar

Thanks for making this available. My system is very similar to your base system. i9-9900k, 64gb RAM, Crucial 1TB SSD, Windows 10, but with an RTX 2080Ti. My scores were: Overall 896.5, Standard 95.9, C4D 95.1, Tracking 71.7. With our systems being so similar, and having the upgraded GPU, is there any way to narrow down why my scores weren't closer to the base, or even higher?

Posted on 2019-01-10 03:44:01

The GPU isn't going to make much of a difference in Ae - in fact, the 1080 Ti benchmarked a bit higher than the RTX cards in our testing: https://www.pugetsystems.co...

There is a lot that could be lowering your scores, ranging from the version of Windows you are on, driver/BIOS version, what motherboard you are using (some are more or less aggressive on Turbo settings), CPU cooling, and what applications you have running in the background. Things like antivirus can be especially bad depending on what software you are using.

Posted on 2019-01-10 18:02:03

I'm not seeing a popup after the tests, but I am getting a log file. Any ideas? Running AE Build 16.0.1

https://uploads.disquscdn.c...

Posted on 2019-01-17 14:44:41
zalmsalade

I have the same problem. No popup but I do get a log file. Also running Mojave and AE 16.0.1.

Posted on 2019-01-18 22:05:51
zalmsalade

The render times are mentioned in the log file and each project is 100 frames long, so you can calculate the framerates manually if you can't wait till this has been fixed.

Posted on 2019-01-20 19:06:52

You mind emailing the BenchLog_XXXXXX.csv and StatusLog_XXXXXX.txt files that are in the benchmark folder to labs@pugetsystems.com ? I haven't been able to replicate the issue on our Macs here, but that might give me enough information to figure out the issue. Thanks!

Posted on 2019-01-21 17:18:00

I have the same issue, run the test but no pop up. I am using After Effects v16.0.1 (Build 48) on a Windows 10 64bit PC.
I do get the log file but it looks like it may not have finished fully, the last entries of the log are:

10:6:1 - Done with RAM Preview Full Res
10:6:2 - Starting Final Render with projnum_render=1
10:6:3 - opening comp Phone Composite Project
10:6:3 - Moving playhead to frame 0
10:6:8 - Show render window
10:6:10 - Deleting render queue
10:6:11 - Add render to queue
10:6:13 - Starting Final Render
10:6:13 - Send Return
10:6:13 - Waiting for Final Render

Does this mean there was no result to the last benchmark, which would probably be the reason I did not get a pop up?

Thanks for your help,
Bradley

Posted on 2019-01-29 10:32:14

Interesting. Good to see it happens regardless of the OS.

One thing I'm wondering - are you leaving the system completely alone while it is running the benchmark, or are you doing other things at the same time? Browsing the web, etc. Basically, does the After Effects window always in focus?

Posted on 2019-01-29 17:17:07
Mark Donohoe

Im having the same problem,
18:0:2 - opening comp Cloud Lightning Project
18:0:2 - Moving playhead to frame 0
18:0:7 - Show render window
18:0:9 - Deleting render queue
18:0:10 - Add render to queue
18:0:12 - Starting Final Render
18:0:12 - Send Enter
18:0:13 - Waiting for Final Render

No final results are generated im on After Effects cc 2019 Windows 64bit PC

Posted on 2019-02-06 09:12:59

Is the render button showing, or had the render started? And again to confirm, the AE window has focus and you are not doing anything else on the system while the benchmark is running?

Posted on 2019-02-06 15:40:24
Joseph Redding

Since I ran the benchmark my after effects still goes fullscreen when I press play. How do I stop this? I've re-installed after effects which didn't solve.

Posted on 2019-01-30 03:44:22

That is one of the settings that is auto-set in order for the benchmark to work properly. It should have been reverted back to your original settings, but sometimes it doesn't for some unknown reason. You can change it in the Preview settings for Spacebar (or whatever key you use). Note that there are a bunch of other settings that are changed that you might want to doublecheck as well. They are all listed on the main "Benchmark Instructions" composition. Re-enabling disk cache and auto save are the two biggest ones I would confirm.

https://uploads.disquscdn.c...

Posted on 2019-01-30 17:47:19
diegosalinas

I have an overall Score of 706, where can I see the score with your machines? Is it possible to have better results with settings in after effects?

Overall: 706.25

Standars: 42.7
C4D 42.7
Tracking 77.6

i9-9920x 3.5ghz
64gb Ram
evga geforce 2080 ti

Thanks!

Posted on 2019-02-04 01:25:37

Right now, we have our results in our Ae hardware articles: https://www.pugetsystems.co...[]=After%20Effects . We only have one article at the moment using this benchmark, however: https://www.pugetsystems.co... .

Eventually we are planning on having some sort of public benchmark result viewer (maybe even allowing public uploads of results), but we have a long backlog of programming projects we need to get through before we can tackle that.

Posted on 2019-02-05 03:40:01
Rens Wegerif

so.... after the benchmark crashed, I decided to continue to work I was inititially doing. But now for every ram preview I make, the magnifitofit thingy is doing his work. Very annoying. How do I fix this?

Posted on 2019-02-05 13:33:17

The benchmark might still be running in the background (it shouldn't be, but programs crashing can be weird) . I would just do a quick reboot.

Posted on 2019-02-05 16:36:30
rdanielsdesign

Hi there. I get an error when I try to run the script:
Unable to execute script at line 15. Function d.getHours is undefined

Please assist. I'm on a Mac btw. Thanks!

Posted on 2019-02-05 17:09:16

That is weird, pretty sure that is a built-in command . You have any extensions or plug-ins installed? If so, you could try uninstalling them or resetting Ae back to default preferences (back them up first if you have anything set that you want to keep).

Posted on 2019-02-05 17:11:38
rdanielsdesign

I do have extensions installed. I'll take a stab at both suggestions and see if either of them fix the issue. Thanks!

Posted on 2019-02-05 17:15:18
Kathryn Thomson

I've tried running the script twice. Both times I get to the "cloud lightning project.mov" render, and it just stops. In status it says "Failed at 00000". 25.33GB available on the drive, so it isn't running out of space. Any ideas? Thanks.

I'm on OSX Mojave 10.14.2

Model Name: MacBook Pro
Model Identifier: MacBookPro11,4
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB

Posted on 2019-02-07 18:40:00

25GB isn't a lot of free space. After Effects might require a certain amount of space in order to start the render. I would try to free up more space (at least 50GB if you can) and see if that solves the issue.

Posted on 2019-02-07 18:44:49
Tom Hall

But my MacPro 2013 kills the benchmark system x 200!
https://uploads.disquscdn.c...

Posted on 2019-02-16 02:39:18

Ha, that's odd. Looks like it didn't actually run the RAM Preview tests. Mind tossing the statuslog_.txt and benchlog_.csv files in an email to mattbach@pugetsystems.com ? I'm guessing it is a setting in your preferences that prevented the benchmark from running properly, but is may be able to figure out a check by reviewing those files.

Posted on 2019-02-16 03:27:27

Thanks for the log files! It looks like the render tests didn't properly run, so the benchmark thinks it was rendering at a couple thousand FPS. I've seen this a few other times, but haven't been able to figure out exactly why it happens. I have a few ideas to add to the next update that might help, however, or at least have it result in an error rather than a bogus score. Thanks again for the help!

Posted on 2019-02-16 03:41:57

Hi! I did a series of tests using this amazing benchmark, I mainly found out the performance gains from RAM frequency and dual channel, but the amount of RAM does not affect performance.
Here is my test result. https://docs.google.com/spr...

In addition, in some cases of 8G RAM, the RAM preview test data is abnormal. This benchmark seems to be 100 frames of comps. I hope to enhance the detection of RAM preview error and additional provide different time lengths comps for different amount of RAM to do stress test. Because there tests have been showing that the amount of RAM will affect the rendering time, I hope to confirm.
Sorry for my bad English, thank you!

Posted on 2019-02-18 22:44:42

In After Effects, more RAM doesn't really improve how fast AE is able to render each individual frame. What it does allow you to do, however, is to store more frames in RAM Preview. For example, if you have a comp that is 1000 frames long, but you only have enough RAM to store 500 frames, by the time you play through the entire comp and start over from the beginning, the frames at the start have already been bumped out of RAM Preview. In that case, you have to completely re-render those frames from scratch rather than just pulling the already rendered frame from RAM. If you have enough RAM to store all the frames, however, Ae doesn't have to keep re-rendering those frames.

This is why there really isn't an answer to "how much RAM do I need for Ae". It really is... as much as possible. It doesn't make Ae render any faster, but it lessens the chances that Ae has to re-render frames that it otherwise could have simply pulled from RAM.

Posted on 2019-02-19 00:52:18

Cool, this also be my conclusion, the amount of RAM will only affect the preview time length.
I made this with reference to Adobe's formula. https://helpx.adobe.com/aft...
https://uploads.disquscdn.c...
Actually it will be less than the theoretical value but it won't be worse, and the preview time length is usually the same. For example, the same test 32G RAM always stops at 1min 50secs (about 3300 frames) on different computers.

Posted on 2019-02-19 02:04:37