Cebolonha

I'm learning Rust, and I was trying to find something fun to code. The last WAN show featured Floatplane's login screen (https://www.floatplane.com/login), which is cool. So I made this: https://github.com/ricardopieper/rust-particles There's probably a lot to refactor, for instance, there are many methods expecting the same arguments on the Renderer impl. But I only have so much time. I made it using Piston. Currently featuring: - Connection strength: The longer 2 particles are near each other, the stronger the connection - Show only the connections near to the mouse position - A little bit of brightness around a particle that depends on the connection strength - The connected line opacity also depends on the connection strength. - Strength gradually increases/decreases depending on the distance. This means the connection lines have a fade-in/fade-out effect. - Particle speed depends on its size (the bigger, the faster) - Particles bounce off of walls The effect is not identical to floatplane's but it's kinda similar.

Also, did you change any graphics settings on the game? Depending on those settings, they can increase the CPU usage.

hwmonitor

You can have a really really long cooking recipe that uses only 1 or 2 ingredients. The dish takes hours and hours to get ready to eat. You can also have a really short recipe that uses 15 ingredients. Just mix them together and it's done in 5 minutes. Recipe is the program, ingredient is the data your program uses.

Which processes are using that much CPU? Just the game?

You can give the CPU just 64bits of data and make the CPU work under 100% load for days. That's why this doesn't matter much. And the result of said process might be just 1 byte of data. The max throughput of an algorithm like this one is almost meaningless. Take, for example, Folding@home. They give you some parameters and a program on which you should donate CPU time, but they aren't doing a whole lot of I/O, if any. I guess you can measure how much data a process is moving around inside the CPU, but that depends on the operations being executed: some are faster than others. Now, achieving max throughput using the least CPU possible IS what you want, and that is really important for web servers and web frameworks. You generally want to saturate your network card before achieving 100% cpu load.

The thing is, we don't measure CPU and GPU speed in terms of transfer speed or I/O. We measure in operations per clock cycle and frequency, and FLOPS/sec, but the latter is only "floating points per second", which is only one kind of operations among others, but is very important anyway.

Trying really hard to understand what IS the question. "I was wondering if we can almost use a cpu without bottlenecks at 40 gigabits per second then what would we need if we were running a cpu not a gpu" Let's break it down: "if we can almost use a cpu without bottlenecks at 40 gigabits per second" - Assumes 40gb/s is near max throughput of CPU - Which CPU? Where does this information come from? I don't know much about hardware, so... let's assume that to be true. Is this applicable to CPUs? Don't we measure operations/clock cycle instead? Doesn't I/O depend on other stuff? I understand we can, like, "sum a list of numbers up to 30GB/s in a modern CPU", but... what are you even doing? "then what would we need" - Need for what? Is 40gb/s not enough for you? What do we need? That's sort of a deep question. Or undefined. "if we were running a cpu not a gpu" - Wait, what? I assumed you were running a CPU to begin with. Where does this GPU come from?

I don't know what's your programming background, but if you're a complete beginner on web dev/programming in general, but has some vague idea of how programming works, you should look into: - What is HTML, CSS, and Javascript? - What is the DOM? - How to query the DOM using CSS selectors, in Javascript? - How to iterate through the DOM elements you found? - How to query for instagram pictures inside a profile/home page? What attributes are common for them? Are all of them links? Images? This is sort of a reverse engineering task. - Why are you having problems opening multiple tabs? Is the browser misbehaving? Can I change some settings? Having a good knowledge of the DOM and CSS selectors will pay a lot of dividends. Javascript will probably be the easiest part. I'm pretty sure you can do it with one line of JS and some browser config.