Just like anything in life, there are necessities or requirements that must be met, if you are building a house, or a computer system. A foundation is required for a house, just as a CPU and mainboard are required for a computer. There are certain things that must be in place if any success is going to be realized. JPS Necessities highlights all of those components, so you are not left out in the dark.
There are Experts everywhere;
When I got into the Computer industry some 40+ years ago, I learned quickly that there were experts in the field who knew exactly what they were doing. They had integrity to an extreme level and understood what customers wanted, whether they were a mom-and-pop shop or part of the worldwide Fortune 500.
Resulting Standards that are built in can be very big keys to success;
There are standards built into everything they designed and implemented across the board, and those standards are just as relevant today as they were back then. Some may be obvious, and then again, some are not. Especially for anyone who hasn’t lived through the computing legacy that has gotten us to this point.
Therefore Standards are always changing to meet new technology as it emerges. JPS Necessities is all about those standards, so let’s get started so you know exactly what they are. I will itemize each one first, and then we can discuss the merits of each.
Therefore, here are those Standards highlighted for JPS Necessities :
- Never design a dead end configuration.
- Always think ahead to the next potential for expansion.
- Upgrade potential must always be built into the current configuration.
- Upgrades must be efficient, easy, self-contained, and always available.
- Upgrades considered are for CPU, GPU, AI processor, Memory, SSD, NVME and Disk
- Keep configurations open for expansion.
- As technology emerges, adapt to the current expansion capability.
- Maximize the current configuration before considering a new footprint.
I will get into the Jps Necessities Standards in a few, but firstly; here is some groundwork from my travels over the last 40 years that is relevant to this topic.
The very best in Technology has always been IBM. They did things even 40 years ago to keep them absolutely on top. And we can learn from the very things they did to maintain their superiority, as all of it is absolutely relevant today.
For instance, they knew from the very beginning that a customer would never buy a dead end configuration (more on that in a bit). There would always be upgrades, and those upgrades had to happen quickly.
It was also known that a customer would always buy the base level first and then grow from there, so they had to put in controls to make that happen fast, easily, and with maximum security.
Things like removing dummy cycles from the control code could give the system a 10–20% boost. Enhancing operand control for storage references would speed up memory access by 15 or 20%. Removing dummy cycles from the I/O processor would speed up the I/O in and out of the system, insuring that data was getting in and out as fast as possible.
Expanding on the topic above, 40 years ago, the processor was controlled by microcode on what to do when. For instance Add register A to Register B and put the result in C. Today its done almost the same using SDROM and Firmware to control the system and tell it what to do.
So when companies (IBM or Intel for example) design a system, it is built to run flat out without any delays embedded anywhere, so they can measure exactly what the max performance can be.
But customers would never start with the top of the line because it was cost-prohibited. They would start at a lower level and that level would have dummy cycles built in to slow it down. When it was time to get higher performance, customers would pay for the next level up, and some of the dummy cycles would be removed by technical personnel.
Each and every one of the techniques indicated above is the default on all systems and is available on every one. For Intel and AMD it requires a chip replacement, I5, I7, AM4 or AM5. For IBM and PCM’s it was a mod to the control code.
This was absolute rocket science, and they had it wired. I was immersed in all of it from the beginning, but I didn’t work for IBM. I worked for a competitor. They invented the game, and Nobody could touch it. If you wanted to compete with them, you had to know how it worked. They had about 50% of the market share, and the rest was split between us and Amdahl. It was a fabulous time, and I was a kid in a candy store!
Fast forward to today, and all of those standards are not only in place but are required to keep pace with technology.
So let’s take a look:
Never Implement a dead end configuration.
In other words, any starting configuration should be good for at least 2 upgrades. And those upgrades can consist of the processor, Memory, SSD/NVME/Disk, and GPU, or combinations thereof. Nobody starts with a max configuration that has nowhere to go other than start over. What seems normal is about 6 months out. The newest technology at initial configuration time will be costly, so by holding off for 6 months, the cost will drop off by about 50%. Perfect time for an upgrade. And then you can do it again in another 6-12 months as it drops off one more time. Any system built should be able to handle such a situation.
Always think ahead to the next potential for expansion.
When you are looking at the first configuration on what is being built, you must consider options at the first upgrade point to insure that;
- You are staying within the processor line on upgrade possibilities (ex., intel with intel, AMD with AMD). I7 with I7 or AM4 with AM4,,, etc. This is relative to the CPU socket, which is built into the motherboard. (ex., If building for Intel I7, then AMD AM4 is not a possible upgrade). Replacing the motherboard on an upgrade is not a good option.
- The next level you are considering is easily available from multiple vendors and must contain a reasonable jump or performance increase.from where you are currently.
- The upgrade being considered should be a reasonable jump, not an extreme jump. Maybe a 25% boost is a good target. A target of 50% boost is probably to extreme and could be a costly consideration.
- Never perform an upgrade that will require a reload of the OS. This one is not known by many people. But a motherboard swap would trigger this or a processor that was not part of the initial offering for the CPU socket. (ex., if a Bios update is mandatory to use the new processor, then an OS reload may be required.)
Upgrade potential must always be built into the current configuration.
This tends to go along with the first one, never building a dead-end configuration. But we do not want to consider an upgrade that is out of line with what is being built. For instance, with memory, the normal way to upgrade is to increase the density of the (dual in-line memory modules (DIMMs), say from 4 GB to 8GB for the same manufacturer.
That would keep the same number of memory slots while simply increasing the density. For processors, it would be similar by going from the Intel I7 entry level, upgrading to mid level or the same consideration for AMD AM4. Any changes such as this can provide upwards to 20% boost. Expecting any more would be out of spec.
Upgrades must be efficient, easy, self-contained, and always available.
Any upgrade being considered should be simple, easy to perform, and any parts required should be easy to obtain from multiple sources. Don’t select parts that are rarely available or hard to get. We want to make this as easy and quick as possible to perform.
The upgrade being considered should be a reasonable jump.
It is very doubtful any upgrade will provide more than a 25% boost. To expect to see more than that for any upgrade, even one containing multiple components (CPU, Memory, GPU) is nothing more than wishful thinking and will not occur.
Never perform an upgrade that will require a reload.
There are certain upgrades that can cause a reload of the system, which is not desirable. Some can be considered simple, and then again, some can be complex. The focus point is whether or not the initial system footprint is being changed / modified and whether or not it fits within the initial guidelines.
Once the system is initialized the first time, the OS keeps track of all system components, and if they get modified beyond acceptable limits, it can alter the makeup of the system and cause a reload requirement. This would mean a new OS would have to be loaded and a new Key required. Obviously, you do not want such a situation.
Upgrades considered are for CPU, GPU, AI processor, Memory, SSD, NVME and Disk
Upgrade or replaceable components are only CPU, GPU, AI processor, Memory and Disk (+SSD, +NVME). Anything falling outside of this is not an option.
A case upgrade could be an option but this has to be looked at closely. For instance, if its to increase Disk space, or make more room available, or provide more clearance for hardware, then that’s reasonable. But if it adds functions to the system that were not available initially, that may trigger an OS reload and is not warranted.
Keep configurations open for expansion
This is directly related to upgrade capability. You never want to close the potential for upgrades on any components until you max out the configuration. You want all components to max out at the same level. For instance, don’t max out the CPU while the GPU is in a minimal state. Once one component is maxed out, it leaves minimal potential for the rest of the system, which means upgrades won’t make any difference.
As technology emerges, adapt to the current expansion capability.
On this one, you have to approach carefully because you could trigger an OS upgrade as a result, which is not ideal. Let’s say your initial configuration that was built had room for processors that were not announced or supported yet. The components were supported up to a certain level.
Then, a couple or so months later, those processors were released and could now be used. Your current configuration may need an OS or Bios upgrade in order to support the new CPU’s. This kind of change could have further-reaching affects on the system, so you have to be careful with the implementation.
Maximize the current configuration before considering a new footprint.
What I’m referring to is making the best use of the current configuration. Don’t go to a brand new configuration until you max out this one. There is life left in the current one, so use it. There’s always a way to get the best use out of it without replacing it and going for something bigger and faster.
On a final note, this community is awesome, and it provides numerous solutions for many of the everyday things you are looking for. No matter what they are, you can find them here. If you just take a little time, you can see that by searching through the categories to the left.
The benefits you receive from this community can be of extreme value in many parts of everyday life that you may be exposed to. What we do here is minimize that exposure in every way we can, whether it’s in the manner in which you need computing capability, the insurance you need for your car or health, or even the services you need for business. We have it all, and the vastness of what we offer is unlimited.
Furthermore, if you are looking for an internet business that creates time freedom and financial freedom, you are in the right place to discover how to make that happen.
Being part of the RRR247 Marketing Family and community, will do exactly that. Go here and get acquainted with us. And you should register to the Email System located to the right of this Article. And reply to any of the emails for direct contact to become a part of this.