Updated WebGL Benchmark Results | Unity Blog

Updated WebGL Benchmark Results · A bit over a year ago, we released a blog post with performance benchmarks for Unity WebGL, to compare WebGL ... UnityBlogNewsTechnologyCommunityGamesManufacturingAECEntertainmentUpdatedWebGLBenchmarkResultsByJonasEchterhoffDecember15,2015inTechnology|4min.readExpandExpandTopicscoveredWebGLShareAbitoverayearago,wereleasedablogpostwithperformancebenchmarksforUnityWebGL,tocompareWebGLperformanceindifferentbrowsers.Wefigureditwastimetorevisitthosebenchmarkstoseehowthenumbershavechanged.MicrosofthassincereleasedWindows10withtheirnewEdgebrowser(whichsupportsasm.jsandisnowenablingitbydefault)-sowewereinterestedtoseehowthatcompetes.Also,wehaveanexperimentalbuildofUnityusingSharedArrayBufferstorunmultithreadedcode,andwewantedtoseewhatkindofperformancegainstoexpect.SowetestedthisinanightlybuildofFirefoxwithSharedArrayBuffersupport. Youarewelcometryourupdatedbenchmarksuiteinyourownbrowserhere. Somenotesonmethodologychangesfromlastyear’sbenchmarks: ThisisusinganupdatedbuildofthebenchmarksuitebuiltinUnity5.3.Youcandownloadtheprojectfolderforthisbenchmarksuitehere,soyoucanexperimentwithitlocally,ortryitonotherplatforms. Thisversionhasbeenstrippedofalloftheartworkandeyecandywehadinthepreviousversion.Theyaddednovaluetothebenchmarks,andtheprogrammerartusedneverlookedgoodanyway.Strippingtheassetsmakesthebuildssmaller,and,moreimportantly,allowsustoredistributetheprojectfolder(seethelinkabove). Weomittedthe“MandelbrotGPU”benchmarkfromthetestsuite,asthattestwouldreallyonlybenchmarktheGPUandnotshowsignificantlydifferentresultsondifferentbrowsers-soitwouldskewtheoverallresultstoshowsmallerrelativedifferences. Weomittedthecomparisontoanativestandalonebuildwedidlastyear,aswefoundthoseresultstobemisleading,asweareoftenrunningdifferentcodeondifferentplatforms(likedifferentshaderimplementationswithdifferentqualitysettings-andalsodifferentscriptingengines). WetestedEdgeHTML12(Edge20.10240.16384.0),whichwasthelatestversionwhenweranthebenchmarks,andwhichdidnothaveasm.jsenabledbydefault-soweturneditonmanually.BynowEdgeHTML13isreleased,whichhasasm.jsenabledbydefault. HerearetheoverallscoresofthedifferentbrowsersrunningthebenchmarksuiteonanWindows10machinewitha3.3.GHzi7CPUandanNvidiaGTX960GPU.Firefox45withSharedArrayBuffershasagreyedoutbar,asthisisanexperimentalbuildofUnityrunningonanightlybuildofFirefox: ExpandHerearethescoresofthedifferentbrowsersrunningthebenchmarksuiteonMacOSXonaRetinaMacBookPro15”withan2.6GHzi7CPU(sowecanseehowSafaricomparesagainsttheotherbrowsers): ExpandHerearethedetailedresultsforeachbenchmarkonwindows(resultsscaledsothatFirefox4132-bitequals1.0foreachtest): ExpandAndonOSX(again,scaledsothatFirefoxequals1.0foreachtest): ExpandHerearetheoverallresultsfromthebenchmarkbuildweshowedlastyearcomparedtotoday,toseehowperformancehaschangedsince(runningonMacOSXonaRetinaMacBookPro15”withan2.6GHzi7CPU): ExpandFinally,hereisabenchmarkofhowlongittakesforUnitycontenttostartup.Thebarsbelowrepresentthetimeinsecondsittookbetweenopeningthebenchmarkprojectandrenderingthefirstframeindifferentbrowsers.Thisisrunningcontentfromalocaldisk,sothetimetodownloadfilesfromthenetworkisignored.Firefoxperformscachingofasm.jscompilationresults,whichmeansthatwhenthesamecontentisrunmorethanonce,compilationcanbeskipped,andsubsequentrunswillloadfaster.Soweareshowingnumbersforbothcold(firstrun)andhot(subsequentrunwithloadingasm.jsfromcache)runsforFirefox: ExpandSomefindings: Firefox4264-bitiscurrentlythefastestshippingbrowserinmostofthebenchmarks.The32-bitversionofFirefoxisnoticeablyslowerthanthe64-bitversion. Edge,asanewcontenderinthesebenchmarkscomesinsecond,withresultsclosetoFirefox(andactuallyfastertheFirefox32-bit)inmostbenchmarks.InbenchmarkswhichstressWebGLrenderingperformance(Particles,AsteroidField),Edgeperformsbestofalltestedbrowsers. SafarideliversperformancecomparabletoChrome,upfromayearagowhenitwassignificantlyslowerthanChrome. InternetExplorer11isfarbehindthepackinjustabouteverything,andistooslowtobeofmuchuserunningUnityWebGLcontent. OurUnitybuildwithSharedArrayBufferssignificantlyimprovesperformance(byseveraltimesinsomeofthebenchmarks).Thisgivesanoutlookoffutureperformancegainstoexpect. Overall,inFirefox,weareseeingan18%performanceincreasecomparedtoourresultsfromoneyearago.SomeofthisisattributabletoFirefox41runningfasterthanFirefox32,thebiggerdifferenceseemstocomefromimprovementsinUnityandtheemscriptencompiler.TheseresultsarefromOSX,whereFirefoxhasbeen64-bitforalongtime.OnWindows,theimprovementsincelastyearwillbebetter,duetothearrivalof64-bitFirefoxbuilds. Lookingatloadtimes,mostmodernbrowsersareabletoloadthebenchmarkprojectinbetween5and7seconds.Firefoxisabletocacheasm.jscompilation,whichbringssubsequentloadsdownto1.5-2seconds. ByJonasEchterhoffDecember15,2015inTechnology|4min.readTopicscoveredWebGLWhatisalegacycomment?ReadaboutournewcommentingsystemhereNavigationNewsTechnologyCommunityGamesManufacturingAECEntertainmentLanguageEnglish中文DeutschEspañol日本語РусскийFrançais한국어PortuguêsMoreReadinglistsRSSfeedsSocialPurchaseProductsSubscriptionAssetStoreResellersEducationStudentsEducatorsCertificationLearnCenterofExcellenceDownloadGetUnityDownloadArchiveBetaProgramUnityLabsLabsPublicationsResourcesLearnplatformCommunityDocumentationUnityQAFAQServicesStatusCaseStudiesMadewithUnityUnityOurCompanyBrandNewsletterBlogEventsCareersHelpPressPartnersInvestorsAffiliatesSecuritySocialImpactPartnersCopyright©2022UnityTechnologiesLegalPrivacyPolicyCookiesDoNotSellMyPersonalInformationCookiesSettings"Unity",Unitylogos,andotherUnitytrademarksaretrademarksorregisteredtrademarksofUnityTechnologiesoritsaffiliatesintheU.S.andelsewhere(moreinfohere).Othernamesorbrandsaretrademarksoftheirrespectiveowners.