[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/vt/ - Virtual Youtubers

Search:


View post   

>> No.8118137 [SPOILER]  [View]
File: 31 KB, 1123x163, 1629289843001.png [View same] [iqdb] [saucenao] [google]
[ERROR]

j*u
>>8111235
>>8111605
>>8115536
I did not read all of what was written, mainly because I am not using the haatonsheet.
Consider the following:
>pic
There is nothing else other than NASFAQ running in that instance of Firefox, and the CPU usage shown is on the lower side of things. It doubles when a buy is occurring in honkbot.
I now understand why some users have a dedicated "NASFAQ ThinkPad".
>>8111855
>you don't need to know the exact prices every 5 seconds, it doesn't move that fast. even the graphs on the market page are only updated every 5-15 minutes.
Really? Explain this:
>.chartjs-render-monitor {
> animation: chartjs-render-animation 0.001s;
>}
>.0.001s
I don't know the first thing about how chartjs works, or how the code that runs this page works in general, but that animation time stuck out. chartjs documentation states that the animation feature is optional. I have 56 graphs open that are apparently animating 1000 times a second. That's 56,000 animations per second.
Over 90% of that CPU usage is JS doing SOMETHING according to Firefox's profiler. Edge was probably sleeping "naughty" threads to keep it from bogging my entire fucking computer.
>>8112143
>all autotrader problems are client-side
The site itself and the auto-trader run like dog shit.
Our choices are:
>Use Chrome
>>It eventually crashes
>Use Edge
>>Good performance, low resource usage, lose cycles regularly, 12m trades
>Use Firefox
>>ABAYO CPU cycles
I mean no ill intentions Devs.
t. retard

Navigation
View posts[+24][+48][+96]