Actually, the performance difference between an i3 and an i7 is negligible.
That chart you pointed at is specifically for gaming. If you're doing parallel compiling, or running multiple VMs, or other easily parallelizable work the fact that an i7 generally has twice as many cores/threads can make a huge difference.
At work we have a 24-core machine that we use for compiling. It makes a huge difference when you're basically building a custom linux distro.
While you don't need to pass arguments, you still need to set environment variables based on user input.
Whoever thought it was a good idea to allow an HTTP request to set environment variables within the HTTP server to arbitrary values wasn't thinking about security.
I have no problems at all with an ISP prioritizing certain types of traffic, but that prioritization should be 1) under the control of the subscriber, and 2) it should *only* affect traffic belonging to that subscriber. My traffic and your traffic should be shaped (as a whole) based on the subscriptions that each of us has paid for.
That is, I could ask my ISP to prioritize my Netflix packets over my bittorrent packets, but if you and I have paid for the same level of service then your VoIP packets shouldn't get priority over my Netflix packets.
If someone complains about an interaction with an officer where the officer's camera has no record of the interaction, the officer is assumed to be guilty.
That should give officers incentive to ensure their cameras are in working order.
I did linux kernel development and low-level posix stuff for over a decade, and there's still plenty of work there. I've now moved on to cloud computing, but on the backend infrastructure side. Lots of stuff happening there too...
Anything performance-sensitive isn't going to use emulation but rather paravirtualization or passthrough of physical devices. Current x86 virtualization is getting pretty good, with minimal hit to CPU-intensive code. As for I/O, you can pass through PCI devices in to the guest for pretty-much native networking performance.
Disk I/O still isn't as good as native, but it's good enough, and most enterprise systems are using ISCSI anyway to allow for efficient live migration.
There are plenty of places where you can't just add more memory...embedded devices in particular. Your phone is limited to 2GB of RAM, and you really don't want any one app chewing it all up. Raspberry Pi, Arduino, BeagleBone, etc. are all relatively limited in terms of resources and to use them efficiently you need to be careful.
Even on really beefy virtualization hosts with a couple hundred GB of RAM, you want to be able to dedicate as much of the resources as possible to the guests, not the host management software--so you need to be able to put strict limits on how much memory the host itself will use under any circumstances.
Apparently there are a number of vaccines being developed. None of them have reached the human trials phase, but several of them have been given to people under in emergency circumstances. The problem is that it requires an official request from the person's government as well as informed consent from the patient. According to the researcher it's hard to get either of these in the area of the current outbreak.
I'm fairly sure that my current house could *not* be rented for cheaper than my mortgage payments, and I'm making bigger payments than strictly necessary because I want to pay it down fast and minimize interest costs.
Also, around here (Canadian prairies) housing prices were pretty stable for decades. Recently they took a jump due to more demand in the market, but that's because people want to move here.
f it does no harm in day to day operations and offers protection when your assumptions fail, why *not* run a software firewall?
Connection tracking can be expensive. If you need that, it's going to cut into the performance of your server, so it can be beneficial to do that on a separate box.
I did mostly linux kernel stuff for over a decade. The vast majority of developers are quite helpful to people with little history in the community. As others have pointed out, generally this sort of stuff is aimed at people/projects that have a history of good work and then fall short of expectations.
If you submit a patch (formatted as per instructions) to the list, generally it will either get ignored (in which case you might want to contact the maintainer for that area) or else you will get some comments. Note that not eveyone's comments count equally--ultimately the subsystem maintainer is the one that will apply the change.
240V would be used for kitchen stove/range, clothes drier, electrical heat (air and water). Some commercial cappucino machines use 240V.
A home shop could very well use 240V for a welder and any number of power tools...lathe, jointer, planer, tablesaw, mortiser, wide belt sander, dust collector, shaper, etc.
In the USA/Canada typical residential setups use two conductors at 120V to ground, but the conductors are out-of-phase so there is 240V between them.
There really isn't any such thing as 110V or 230V in the USA/Canada, both of which you'll sometimes see referenced. 208V does exist, it's the difference between two legs of a 3-phase setup where each leg is at 120V to ground.
Actually, the performance difference between an i3 and an i7 is negligible.
That chart you pointed at is specifically for gaming. If you're doing parallel compiling, or running multiple VMs, or other easily parallelizable work the fact that an i7 generally has twice as many cores/threads can make a huge difference.
At work we have a 24-core machine that we use for compiling. It makes a huge difference when you're basically building a custom linux distro.
Even when using sendfile() in linux, the disk does a DMA transfer into RAM, and the NIC does a DMA transfer out of RAM.
While the CPU is not involved in copying the data, it still goes into RAM.
The user input is in the form of specially-crafted HTTP headers in the HTTP request that cause environment variables to be set on the server.
While you don't need to pass arguments, you still need to set environment variables based on user input.
Whoever thought it was a good idea to allow an HTTP request to set environment variables within the HTTP server to arbitrary values wasn't thinking about security.
Sony Xperia Z3 Compact
I have no problems at all with an ISP prioritizing certain types of traffic, but that prioritization should be 1) under the control of the subscriber, and 2) it should *only* affect traffic belonging to that subscriber. My traffic and your traffic should be shaped (as a whole) based on the subscriptions that each of us has paid for.
That is, I could ask my ISP to prioritize my Netflix packets over my bittorrent packets, but if you and I have paid for the same level of service then your VoIP packets shouldn't get priority over my Netflix packets.
Typically the scoopers carry a tank of fire retardant concentrate that gets injected into the scooped water.
...and the DC-10 can deliver as much water as five of the largest water scoopers.
I question that. The Martin Mars scooper holds 7200 US gallons.
Most providers of "cloud" services are *not* free. You pay for time, workload, network, storage, etc.
In IaaS (infrastructure as a service) you're basically just renting time/space/bandwidth on someone else's equipment.
To an independent body that doesn't report to the police.
If someone complains about an interaction with an officer where the officer's camera has no record of the interaction, the officer is assumed to be guilty.
That should give officers incentive to ensure their cameras are in working order.
That last sentence should have been, "....remain relevant for the next two years, much less the next 20."
They make some decent stainless steel woodworking rasps and other woodworking tools that require some hand-work.
I did linux kernel development and low-level posix stuff for over a decade, and there's still plenty of work there. I've now moved on to cloud computing, but on the backend infrastructure side. Lots of stuff happening there too...
I'm pretty sure that most of the main guys working on Wayland are guys that have been involved with X for a long time.
I live in the Canadian prairies. Our block heater is 400W. When it's -40, you need the heat.
If you didn't already know about this, and didn't have a network connection, how would you discover this?
(And yes, the same complaint holds true for linux as well....)
Anything performance-sensitive isn't going to use emulation but rather paravirtualization or passthrough of physical devices. Current x86 virtualization is getting pretty good, with minimal hit to CPU-intensive code. As for I/O, you can pass through PCI devices in to the guest for pretty-much native networking performance.
Disk I/O still isn't as good as native, but it's good enough, and most enterprise systems are using ISCSI anyway to allow for efficient live migration.
There are plenty of places where you can't just add more memory...embedded devices in particular. Your phone is limited to 2GB of RAM, and you really don't want any one app chewing it all up. Raspberry Pi, Arduino, BeagleBone, etc. are all relatively limited in terms of resources and to use them efficiently you need to be careful.
Even on really beefy virtualization hosts with a couple hundred GB of RAM, you want to be able to dedicate as much of the resources as possible to the guests, not the host management software--so you need to be able to put strict limits on how much memory the host itself will use under any circumstances.
Apparently there are a number of vaccines being developed. None of them have reached the human trials phase, but several of them have been given to people under in emergency circumstances. The problem is that it requires an official request from the person's government as well as informed consent from the patient. According to the researcher it's hard to get either of these in the area of the current outbreak.
I'm fairly sure that my current house could *not* be rented for cheaper than my mortgage payments, and I'm making bigger payments than strictly necessary because I want to pay it down fast and minimize interest costs.
Also, around here (Canadian prairies) housing prices were pretty stable for decades. Recently they took a jump due to more demand in the market, but that's because people want to move here.
f it does no harm in day to day operations and offers protection when your assumptions fail, why *not* run a software firewall?
Connection tracking can be expensive. If you need that, it's going to cut into the performance of your server, so it can be beneficial to do that on a separate box.
I did mostly linux kernel stuff for over a decade. The vast majority of developers are quite helpful to people with little history in the community. As others have pointed out, generally this sort of stuff is aimed at people/projects that have a history of good work and then fall short of expectations.
If you submit a patch (formatted as per instructions) to the list, generally it will either get ignored (in which case you might want to contact the maintainer for that area) or else you will get some comments. Note that not eveyone's comments count equally--ultimately the subsystem maintainer is the one that will apply the change.
240V would be used for kitchen stove/range, clothes drier, electrical heat (air and water). Some commercial cappucino machines use 240V.
A home shop could very well use 240V for a welder and any number of power tools...lathe, jointer, planer, tablesaw, mortiser, wide belt sander, dust collector, shaper, etc.
In the USA/Canada typical residential setups use two conductors at 120V to ground, but the conductors are out-of-phase so there is 240V between them.
There really isn't any such thing as 110V or 230V in the USA/Canada, both of which you'll sometimes see referenced. 208V does exist, it's the difference between two legs of a 3-phase setup where each leg is at 120V to ground.