Difference of Core i3, Core i5 & Core i7

Difference of Core i3, Core i5 & Core i7

 During Security Software installation we are giving some pre requisite to customer / we assumed what type of System hardware is required, accordingly get costing from Vendor. If you are System integrator, your design team must know about the processor.

Intel Core i³ Processor

This particular Intel processor is the entry level processor of this new series of Intel processors. While it may not be the fastest one of the bunch, it can get the job done, at least for most applications.

Mind you, if you need high speed, I suggest one of the other processors that I will unveil in front of your eyes later on in this post. Here’s some of the Core i3 features.

·        Uses 4 threads. Yes, it uses hyper-threading technology which is the latest craze due to its improved efficiency over earlier processors that were put on the market.

·        This processor consists of 2-4 cores, depending on which one you get your hands on.

·        Contains A 3-4 MB Cache

·        Uses less heat and energy than earlier processors, which is always a good thing in this day and age.

Intel Core i⁵ Processor

·        This is the mid-size processor of this bunch, recommended for those who demand a little speed, but not quite enough where the user will be running resource-intensive applications.

·        As with the Core i3 processor, this comes with 2-4 cores, the main difference is that it has a higher clock speed than the Core i3.

·        This is also a heat and energy efficient processor, but it does seem to be better at this particular job than the Core i3 processor.

·        The number of threads used in this is no different than the Core i3 with 2-4 threads, and it also uses hyper threading technology for a boost in performance.

·        The cache of the Core i5 is bigger than the Core i3, it’s at 3-8 MB.

·        The Core i5 is where the turbo mode is made available, this provides users with the opportunity to turn off a core if it’s not being utilized.

Intel Core i⁷ Processor

·        This is for the users that demand power, yes it does provide more power and if Tim Allen gets one of these, this would be the beast that he gets his hands on. Great for gamers and other resource intensive users. 

·        The cache on this one is 4-8 MB.

·        This processor comes with 8 threads, definitely enough to get the job done quickly, maybe even at the speed of light if you’re lucky.  And yes it also utilizes hyperthreading technology.

·        You will have four cores to take advantage of with this particular series.

·        And just like the other ones in this Intel series of processors, it is more energy efficient and produces less heat.

Below reviews the specifications (high-level) of 10^th Gen Intel Core i7 processors as of late 2020.^*

	Cores/ Hyperthreading	Base Frequency	Maximum Turbo Frequency	Cache
Core i7 Laptops	4-8 / Yes	1.00-2.70 GHz	3.80-5.10 GHz	8-16 MB
(10th Generation)
Core i7 Desktops	8 / Yes	2.00-3.80 GHz	4.50-5.10 GHz	16 MB
(10th Generation)

The Intel Core i9 is often called Intel's processor line for "CPU enthusiasts," the early-adopters who always demand the industry’s latest and greatest. A Core i9-powered desktop or i9-powered laptop is great for users whose work requires extremely advanced computing capabilities (editing 4K video, for example). It’s also popular with high-end gamers who play live-action, multi-player, VR-based titles that can benefit from a CPU with hyper-fast cycle times and high core-thread counts.

The Core i9 debuted in 2017 along with a new socket-motherboard combination to support it. As this FAQ was written, the i9 had evolved to a deliver up to10 cores and 20 threads (desktop version). It costs more than the other members of the Intel Core family, but for certain applications, games and other workloads, the difference could be meaningful.

Table below lists the top-level specifications of Intel Core i9 processors (10^th gen) as of late 2020.

	Cores/ Hyperthreading	Base Frequency	Maximum Turbo Frequency	Cache
Core i9 Laptops	8 / Yes	2.40 GHz	5.30 GHz	16 MB
(10th Generation)
Core i9 Desktops	10 / Yes	1.90-3.70 GHz	4.60-5.30GHz	20 MB
(10th Generation)

Here are some broad statements addressing the comparative cost of Intel Core i9-enabled systems versus models with lesser processors, along with the kinds of users (and use cases) that are most likely to benefit from an advanced Core i9 PC:

• Core i⁹ PC – Cost category
• The Core i9 is the “enthusiast” line of Intel Core CPUs
• Core i⁹ PC – Typical users
• Processor early-adopters
• Users of extremely demanding software
• Gamers who always want the latest/greatest
• Workstation users, server operators, etc.
• Core i⁹ PC – Use cases
• Everything the lesser Intel processors can do plus core-intensive activities such as editing huge video files, rendering complex engineering designs, acting as a server, and so on.

Backup and Archiving

Backup and archiving are always mentioned together, as both of these technologies support primary data storage. However, the commonalities end over here and cannot be carried forward. But in enterprise IT world it is often observed that archive is analogous to backup.

Simply put, backup and archive are not the same and here’s why explained in simple terms-

Data Backup

Data backup is intended to recover individual lost or corrupt files, or individually corrupt operating system instances. The backed up data has both active and inactive information which encompasses all of your production data. This backup set is useful for purposes of recovery in case of the original copy of data is lost or becomes inaccessible due to reasons. It is always critical that a backup is a copy of production data and the actual data still resides on the production storage systems.

Backups are historically being optimized for large scale recoveries. They are written in large blocks to dedicated hardware like tape libraries or deduplicated disk backup appliances.

On a typical note, these backups are scheduled, often every 24 hours, sometimes more frequently, even hourly with some continuous data protection solutions. The data driven by a backup is stored on a tape or a disk solution or off site like a cloud platform. Restoration from backup can be a complex and lengthy process depending on the volume of data to be restored.

Data archiving

Data archiving on the other hand, is data meant for long term retention, typically for compliance purposes in regulated industries such as finance and legal sectors. These are actually designed with very different access profiles. These systems typically store individual data objects such as files, databases or email messages and usually also capture metadata associated with each item.  The result is that an archive can provide immediate granular access to stored information and so accessing an individual file or email is typically very easy in an archive system.

Generally, archiving solutions which retain and index all copies and versions of a document, file, or email, making them easily are expected to be rapidly retrievable by end users rather than IT admins.

So, please do not treat your backups as archives or vice versa as same, as they serve for different purposes.

Embedded Network Video Recorders (NVRs) over Windows-based NVRs Comparison

Embedded Network Video Recorders (NVRs) over Windows-based NVRs Comparison

Video surveillance users who opt for an NVR using an embedded, dedicated Linux operating system within a self-contained unit will benefit from performance which is superior to that offered by a Windows-based NVR in terms of ease of use, system stability and decoding capability.

Embedded NVRs are distinguished from WINDOWS-based NVRs primarily on how they operate and the features they provide. The stand-alone NVR comes in a single, compact enclosure. By contrast, a WINDOWS-based NVR is a peripheral addition to a system involving a CPU, keyboard and monitor. In confined locations, an embedded unit performs a similar if not wider range of functions while occupying less space. Embedded NVRs have overcome their perceived shortcomings in terms of storage capacity and types of storage medium through use of devices including IP-SAN, eSATA, NAS (network-attached storage) and Fire wire.  Furthermore, embedded NVRs can support interfaces to other surveillance devices which can be conveniently integrated with alarm systems and access control systems as well as PTZ remote control systems.

Functions common to the two approaches
Some common functions between the two video recording solutions in the surveillance market, it will be useful to list the core functions that are common to both approaches. These include: recording; archiving; display; playback; search on parameters such as date, timeline and event; camera management; triggered recording on prescribed events and export to removable media. NVRs are also usually expected to be able to handle VoIP packets. Once digitalized video has been streamed, end-users expect to be able to treat it like any other network data, viewing it locally, on LANs and remotely from web browsers. They also expect to be able to exercise PTZ control over cameras remotely, configure settings and even perform upgrades remotely.

Storage

Although NVRs have ample internal recording and storing space, the PC-based systems offer as much as seven times more storage, when compared to an NVR. This advantage is, however, addressed by NVRs, through the provision for external storage options (USB storage devices, eSATA devices, Firewire storage devices, NAS appliances, etc.)

Reliability
The precise architecture of the embedded NVR units makes them less prone to crash. However, the WINDOWS methodology for NVRs is certainly 'open' in terms of the addition of external storage, installation of software etc. The controls are embedded into the NVR; they are an integral part of the panel rather than an adjunct, and the activity of operators can therefore be more easily restricted to legitimate usage.

Stability
Unlike a WINDOWS-based unit which is likely to run a range of Windows™ applications, an embedded NVR benefits from the stability that comes with Linux code which is optimized to run only applications relevant to the surveillance tasks required. An embedded operating system contains only the software components necessary for the specific functions of the NVR, and the unit will be supplied with optimum configurations straight from the factory after rigorous testing.

Scalability

An NVR is designed to offer optimal performance for a set number of cameras, and is normally less scalable than a WINDOWS -based system. This makes the unit suitable for smaller systems where the number of cameras stays within the limits of an NVR’s designed capacity.

Boot Time

The NVR runs an embedded operating system as compared to a WINDOWS -based system, which needs to run an application under the Windows OS before it begins recording. This means that the NVR will start faster as compared to the WINDOWS -based system; which will take longer to load.

Complex decoding
Embedded NVRs consistently outperform WINDOWS-based solutions in their ability not only to perform complex decoding but also to give the user reliable video playback and preview. Currently, certain NVRs are among the few units which can perform both local decoding and playback, with decoding of up to 16 channels at 1080p being achievable. The processing demands made on a WINDOWS-based solution to achieve comparable performance are far higher than those required of an embedded device, and necessitate powerful, expensive CPUs.

Power consumption and manufacturing carbon footprint
Embedded technologies are helping the surveillance industry to go green in marked contrast with the WINDOWS approach. The power consumption of an embedded NVR is approximately 70W which is less than an incandescent light bulb. By contrast, the likely power consumption of a WINDOWS capable of running an NVR is approximately 200 watts and together with a large enterprise-grade monitor, the total figure will be about 300 watts. For any end-user mindful of their carbon footprint, these figures alone must do much to settle the debate.

Ease of Use
Embedded NVRs can have operating panels based on the very best intuitive design principles. LED signals, digital inputs and outputs, push buttons and dials can all be arranged in an ergonomic way. Sensible layout in a panel approach rather than a screen-based GUI can replicate the ease of use found in a WINDOWS but without the vulnerabilities described above.

ONVIF

Linux based Network Video Recorder for multi-brand and ONVIF compliant multi-megapixel IP cameras and basic automation.

NAS, DAS, or SAN? - Choosing the Right Storage Technology ?

Data is unquestionably the lifeblood of today's digital organization. Storage solutions remain a top priority in IT budgets precisely because the integrity, availability and protection of data are vital to business productivity and success. But the role of information storage far exceeds day to day functions. Enterprises are also operating in an era of increased uncertainty. IT personnel find themselves assessing and planning for more potential risks than ever before, ranging from acts of terrorism to network security threats. A backup and disaster recovery plan is essential, and information storage solutions provide the basis for its execution.

Businesses are also subject to a new wave of regulatory compliance legislation that directly affects the process of storing, managing and archiving data. This is especially true for the financial services and healthcare industries, which handle highly sensitive information and bear extra responsibility for maintaining data integrity and privacy.

Although the need for storage is evident, it is not always clear which solution is right for your organization. There are a variety of options available, the most prevalent being direct-attached storage (DAS), network-attached storage (NAS) and storage area networks (SAN). Choosing the right storage solution can be as personal and individual a decision as buying a home. There is no one right answer for everyone. Instead, it is important to focus on the specific needs and long-term business goals of your organization. Several key criteria to consider include:
• Capacity - the amount and type of data (file level or block level) that needs to be stored and shared
• Performance - I/O and throughput requirements
• Scalability - Long-term data growth
• Availability and Reliability - how mission-critical are your applications?
• Data protection - Backup and recovery requirements
• IT staff and resources available
• Budget concerns
While one type of storage media is usually sufficient for smaller companies, large enterprises will often have a mixed storage environment, implementing different mediums for specific departments, workgroups and remote offices. In this paper, we will provide an overview of DAS, NAS and SAN to help you determine which solution, or combination of solutions, will best help you achieve your business goals.


DAS: Ideal for Local Data Sharing Requirements

Direct-attached storage, or DAS, is the most basic level of storage, in which storage devices are part of the host computer, as with drives, or directly connected to a single server, as with RAID arrays or tape libraries. Network workstations must therefore access the server in order to connect to the storage device. This is in contrast to networked storage such as NAS and SAN, which are connected to workstations and servers over a network. As the first widely popular storage model, DAS products still comprise a large majority of the installed base of storage systems in today's IT infrastructures. Although the implementation of networked storage is growing at a faster rate than that of direct-attached storage, it is still a viable option by virtue of being simple to deploy and having a lower initial cost when compared to networked storage. When considering DAS, it is important to know what your data availability requirements are. In order for clients on the network to access the storage device in the DAS model, they must be able to access the server it is connected to. If the server is down or experiencing problems, it will have a direct impact on users' ability to store and access data. In addition to storing and retrieving files, the server also bears the load of processing applications such as e-mail and databases. Network bottlenecks and slowdowns in data availability may occur as server bandwidth is consumed by applications, especially if there is a lot of data being shared from workstation to workstation.

DAS is ideal for localized file sharing in environments with a single server or a few servers - for example, small businesses or departments and workgroups that do not need to share information over long distances or across an enterprise. Small companies traditionally utilize DAS for file serving and e-mail, while larger enterprises may leverage DAS in a mixed storage environment that likely includes NAS and SAN. DAS also offers ease of management and administration in this scenario, since it can be managed using the network operating system of the attached server. However, management complexity can escalate quickly with the addition of new servers, since storage for each server must be administered separately.

From an economical perspective, the initial investment in direct-attached storage is cheaper. This is a great benefit for IT managers faced with shrinking budgets, who can quickly add storage capacity without the planning, expense, and greater complexity involved with networked storage. DAS can also serve as an interim solution for those planning to migrate to networked storage in the future. For organizations that anticipate rapid data growth, it is important to keep in mind that DAS is limited in its scalability. From both a cost efficiency and administration perspective, networked storage models are much more suited to high scalability requirements.

Organizations that do eventually transition to networked storage can protect their investment in legacy DAS. One option is to place it on the network via bridge devices, which allows current storage resources to be used in a networked infrastructure without incurring the immediate costs of networked storage. Once the transition is made, DAS can still be used locally to store less critical data.
NAS: File-Level Data Sharing Across the Enterprise

Networked storage was developed to address the challenges inherent in a server- based infrastructure such as direct-attached storage. Network-attached storage, or NAS, is a special purpose device, comprised of both hard disks and management software, which is 100% dedicated to serving files over a network. As discussed earlier, a server has the dual functions of file sharing and application serving in the DAS model, potentially causing network slowdowns. NAS relieves the server of storage and file serving responsibilities, and provides a lot more flexibility in data access by virtue of being independent.

NAS is an ideal choice for organizations looking for a simple and cost-effective way to achieve fast data access for multiple clients at the file level. Implementers of NAS benefit from performance and productivity gains. First popularized as an entry-level or midrange solution, NAS still has its largest install base in the small to medium sized business sector. Yet the hallmarks of NAS - simplicity and value - are equally applicable for the enterprise market. Smaller companies find NAS to be a plug and play solution that is easy to install, deploy and manage, with or without IT staff at hand. Thanks to advances in disk drive technology, they also benefit from a lower cost of entry.

In recent years, NAS has developed more sophisticated functionality, leading to its growing adoption in enterprise departments and workgroups. It is not uncommon for NAS to go head to head with storage area networks in the purchasing decision, or become part of a NAS/SAN convergence scheme. High reliability features such as RAID and hot swappable drives and components are standard even in lower end NAS systems, while midrange offerings provide enterprise data protection features such as replication and mirroring for business continuance. NAS also makes sense for enterprises looking to consolidate their direct-attached storage resources for better utilization. Since resources cannot be shared beyond a single server in DAS, systems may be using as little as half of their full capacity. With NAS, the utilization rate is high since storage is shared across multiple servers.

The perception of value in enterprise IT infrastructures has also shifted over the years. A business and ROI case must be made to justify technology investments. Considering the downsizing of IT budgets in recent years, this is no easy task. NAS is an attractive investment that provides tremendous value, considering that the main alternatives are adding new servers, which is an expensive proposition, or expanding the capacity of existing servers, a long and arduous process that is usually more trouble than it's worth. NAS systems can provide many terabytes of storage in high density form factors, making efficient use of data center space. As the volume of digital information continues to grow, organizations with high scalability requirements will find it much more cost-effective to expand upon NAS than DAS. Multiple NAS systems can also be centrally managed, conserving time and resources.

Another important consideration for a medium sized business or large enterprise is heterogeneous data sharing. With DAS, each server is running its own operating platform, so there is no common storage in an environment that may include a mix of Windows, Mac and Linux workstations. NAS systems can integrate into any environment and serve files across all operating platforms. On the network, a NAS system appears like a native file server to each of its different clients. That means that files are saved on the NAS system, as well as retrieved from the NAS system, in their native file formats. NAS is also based on industry standard network protocols such as TCP/IP, FC and CIFS.

SANs: High Availability for Block-Level Data Transfer

A storage area network, or SAN, is a dedicated, high performance storage network that transfers data between servers and storage devices, separate from the local area network. With their high degree of sophistication, management complexity and cost, SANs are traditionally implemented for mission-critical applications in the enterprise space. In a SAN infrastructure, storage devices such as NAS, DAS, RAID arrays or tape libraries are connected to servers using Fibre Channel. Fibre Channel is a highly reliable, gigabit interconnect technology that enables simultaneous communication among workstations, mainframes, servers, data storage systems and other peripherals. Without the distance and bandwidth limitations of SCSI, Fibre Channel is ideal for moving large volumes of data across long distances quickly and reliably.

In contrast to DAS or NAS, which is optimized for data sharing at the file level, the strength of SANs lies in its ability to move large blocks of data. This is especially important for bandwidth-intensive applications such as database, imaging and transaction processing. The distributed architecture of a SAN also enables it to offer higher levels of performance and availability than any other storage medium today. By dynamically balancing loads across the network, SANs provide fast data transfer while reducing I/O latency and server workload. The benefit is that large numbers of users can simultaneously access data without creating bottlenecks on the local area network and servers.

SANs are the best way to ensure predictable performance and 24x7 data availability and reliability. The importance of this is obvious for companies that conduct business on the web and require high volume transaction processing. Another example would be contractors that are bound to service-level agreements (SLAs) and must maintain certain performance levels when delivering IT services. SANs have built in a wide variety of failover and fault tolerance features to ensure maximum uptime. They also offer excellent scalability for large enterprises that anticipate significant growth in information storage requirements. And unlike direct-attached storage, excess capacity in SANs can be pooled, resulting in a very high utilization of resources. There has been much debate in recent times about choosing SAN or NAS in the purchasing decision, but the truth is that the two technologies can prove quite complementary. Today, SANs are increasingly implemented in conjunction with NAS. With SAN/NAS convergence, companies can consolidate block-level and file-level data on common arrays.

Even with all the benefits of SANs, several factors have slowed their adoption, including cost, management complexity and a lack of standardization. The backbone of a SAN is management software. A large investment is required to design, develop and deploy a SAN, which has limited its market to the enterprise space. A majority of the costs can be attributed to software, considering the complexity that is required to manage such a wide scope of devices. Additionally, a lack of standardization has resulted in interoperability concerns, where products from different hardware and software vendors may not work together as needed. Potential SAN customers are rightfully concerned about investment protection and many may choose to wait until standards become defined.

Conclusion

With such a variety of information storage technologies available, what is the best way to determine which one is right for your organization? DAS, NAS and SAN all offer tremendous benefits, but each is best suited for a particular environment. Consider the nature of your data and applications. How critical and processing-intensive are they? What are your minimum acceptable levels of performance and availability? Is your information sharing environment localized, or must data be distributed across the enterprise? IT professionals must make a comprehensive assessment of current requirements while also keeping long-term business goals in mind.

Like all industries, storage networking is in a constant state of change. It's easy to fall into the trap of choosing the emerging or disruptive storage technology at the time. But the best chance for success comes with choosing a solution that is cost-correct and provides long term investment protection for your organization. Digital assets will only continue to grow in the future. Make sure your storage infrastructure is conducive to cost-effective expansion and scalability. It is also important to implement technologies that are based on open industry standards, which will minimize interoperability concerns as you expand your network.

How To Setup Two or More Routers Together

One of the most common issues people encounter is when they have more than one router hooked up. Sometimes people don't realize their modem is also a router (Such as DSL) and other times people hook up an extra router to use things their router/modem doesn't have, such as wireless.

So now with 2 or more routers hooked up people start to realize port forwarding & port triggering isn't working. This is because they are only setting up the port forwarding or triggering in one router, which is what they should be doing! Now let me explain, no one wants to setup port forwarding & triggering rules in two or more routers, they should only need to do it in one, making things simple. But you may ask "If I have more than one router how can I keep it simple?" The answer: DMZ

First off DMZ is supported by nearly every router/modem out there. What DMZ does is allow you to tell the router to forward all incoming connections to a single IP address. So in this case we will setup DMZ in the first router to point to the second router. Now all incoming connections are sent to the 2nd router and thus your port forwarding & triggering will work again.

So here is a quick example. I log into router 1 and go to the DMZ settings and put the WAN IP address of the 2nd router there. Now router 1 is out of the way for port forwarding and triggering as all incoming connections are now being forwarded to router 2. Now in router 2 I can setup my port forwarding & triggering rules just like normal.

So here is a quick step by step.
Step 1. Login into your Router
Step 2. Find the status page that shows the WAN/Internet IP address and write it down. (The Gateway IP will be the IP needed to log into the first router/modem.)
Step 3. Log into the first router/modem now.
Step 4. Find the DMZ page
Step 5. Enter the IP you wrote down into the DMZ page and enable DMZ.
Step 6. Save and you’re done.

Quick Tip: You should setup a static WAN IP address for router 2. If you leave it on DHCP the IP could change thus breaking the DMZ and of course breaking the port forwarding & triggering. This doesn't happen very often, but it is always a possibility.

If you want to Setup 3 routers at home. Here is my plan to setup. Please let me know if it make sense.

1.    SMC. It is a modern with router. It locates in the first floor, Rogers cable connected to this router. It is the main router to connect outside. I turned off the wireless on the router. It has 4 ports connected to SMC all with wires. First one connect to D-615(second router) Second one connect to D-815(third router) Third one connect to WD Mybook live(NAS HHD) Fourth one connect to TV player

2.    DLink 615. It is a wireless router. It located in the first floor as well, but close to bedroom. It has 4 ports, but I only use 3 of them connected to PC. Also there are wireless device need connect to this router as well.

3.    DLInk 815. It is a wireless router. It located in the second floor. It connected with 3 PCs and also accept wireless connection. The signal in second floor is very weak if using D-615 wireless connection.

I setup the SMC to 192.168.0.1 with DHCP, D-615 to 192.168.2.1 with DHCP and D-815 to 192.168.1.1. I cannot get rid of the second router, since SMC doesn't have enough wired port. And I need to D-815 because the signal problem. Wondering if this gonna work? Thanks.