Wireless Charging Wastes Way More Electricity Than Wired, Here’s Why



Wireless charging has become ubiquitous in recent years, with companies like Apple, Samsung and Google all embracing the technology. The benefit is obvious. It’s easier to plop a device on a charging pad than it is to wiggle in a USB-C cable. 

Despite the convenience, there are some downsides with wireless charging tech. Generally speaking, wireless charging is inefficient, wasting more energy than wired charging. Let’s get into the why of it all and detail other risks associated with wireless charging.

How is wireless charging less efficient?

Wireless chargers use more power to completely charge a device, when compared to a cable. A modern smartphone is a great example of this. Charging a smartphone with a wire from zero to 100 percent takes around 15Wh (watt-hours measure the amount of energy needed for a device to run for an hour). The same phone will require around 21Wh (40 percent more) to juice up via a wireless charger, according to a 2020 study by the enterprise platform OneZero. That number could vary based on the charger and how you use it — a 2024 test by iFixit found the energy gap between Apple’s MagSafe charger and wired charger to be slightly better at around 36 percent more power used, and also showed how misalignment on a charging pad could halve the efficiency of a wireless charger.

Wireless chargers also generate and waste more heat than wired chargers. Charging pads get pretty hot during use, which is a sure sign of wasted energy.

Is this discrepancy a big deal?

Yes and no. A daily difference of around 6Wh isn’t that big of a deal when considering a single wired charger versus a single wireless charger. However, it adds up when considering every wired charger versus every wireless charger. A year of charging up a smartphone with a cable takes around 5.5 kilowatt-hours (kWh) and that shoots up to 7.6kWh with a wireless charger.

Studies have indicated that 30 to 66 percent of smartphone owners use wireless charging pads and related accessories at home, according to the Wireless Power Consortium and the Deloitte Mobile Consumer Survey UK. There are around 7.6 billion smartphones in the world. If 30 percent of those smartphones are being charged wirelessly that would indicate an annual global power waste of 4,830GWh. This amount of energy could power hundreds of thousands of homes for a year. Wireless charging products are becoming more popular every year, so this metric will only go up.

Why is wireless charging less efficient than wired charging?

Wireless chargers transfer power through electromagnetic induction. This is simply not as efficient as a direct charge, as the energy has to go through more steps to be usable. There’s also an air gap between the phone and the charger, which lets heat escape. 

This is compounded by phone cases and the like, which increase the air gap. All told, wireless chargers lose anywhere from 20 to 30 percent of power throughout the whole process, due to heat dissipation. That’s on top of the 5-10 percent of losses that all chargers incur by converting the AC energy coming from an outlet to DC.

Are there any dangers when charging wirelessly?

The heat that wireless chargers produce could degrade your phone’s battery over time. Modern phones have safety mechanisms in place to prevent overheating that could seriously degrade your battery or result in a fire hazard. These mechanisms, however useful, will result in your charging session being throttled to a lower speed if the battery reaches high temperatures around the 45C (113F) mark. Make sure to use the charging pad in a well-ventilated area and never put it underneath something like a blanket or pillow. 

There are hundreds of chargers out there, and they aren’t all created equal. Cheap, unbranded chargers may lack crucial safety features like temperature sensors and foreign object detection. To that end, it can be dangerous to place metal objects between the phone and the charger. Finally, some powerful chargers can interfere with medical devices like pacemakers, as they generate magnetic fields strong enough to trigger the health aide’s “magnet mode” and alter the pacing rate. 

Is wireless charging bad for the environment?

Wireless charging uses more energy than wired charging, so it has a higher environmental impact than wired charging. Additionally, the charging pads will eventually become electronic waste. The technology’s tendency to degrade lithium-ion batteries over time could, in extreme examples, lead consumers to swap out their phones earlier than usual, which would have an additional environmental impact.

Is wireless charging getting more efficient?

Wireless charging is getting more efficient, which is great news. This is due to better coil alignment and industry standards set by MagSafe and Qi2 products. However, it’s highly improbable that wireless charging ever catches up to wired charging. A wired connection is simple. It’s a plug that goes from point A to point B. Wireless charging requires energy to transmit through magnetic fields.

Are there negatives to wired charging?

Despite some obvious benefits, there are some drawbacks to going with a wired charging solution. Cables degrade over time, and technology changes can force users to upgrade. We all have that cardboard box in the basement filled with dozens and dozens of barely functioning cables of various types. Also, charging ports can wear out after several years of use. Finally, it’s just more fun to plop a smartphone on a magical pad, when compared to plugging in a cord.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What is a star schema?

Star schemas are the most basic structure for storing data in a data warehouse. A star schema’s centre is made up of one or more “fact tables” that index a series of “dimension tables.” To fully comprehend star schemas, as well as snowflake schemas, fact tables and dimension tables must be thoroughly examined.

What is a Snowflake schema?

A snowflake schema’s purpose is to normalise the denormalized data in a star schema. This eliminates the write command slowdowns and other issues that are commonly associated with “star schemas.”

A “multi-dimensional” framework seems to be the snowflake schema. At its heart are fact tables which communicate the data gleaned in dimension tables, which radiate upwards and like a star. The snowflake schema’s dimension tables, on the other hand, start dividing themselves into multiple tables. This results in the snowflake pattern.

Become a Snowflake Certified professional by learning this HKR Snowflake Training !

Snowflake Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

Star schema vs snowflake schema:

The following are the key differences between the start schema and snowflake schema across multiple factors.They are:

1. Working and organizing the data

Data orgaing in star schema:

The goal of a star schema is to separate numerical “fact” data about a business from descriptive, or “dimensional” data. Price, weight, speed, and quantities that is, data in a numerical format will be included in fact data. Colors, model names, geographical locations, employee names, salesperson names, and so on will be included in dimensional data, in addition to numerical information.

The factual data is organised into fact tables, while the dimensional data is organised into dimension tables. In the data warehouse, fact tables are the integration points at the centre of the star schema. They enable machine learning tools to analyse the data as a whole, and they allow other business systems to access the data as well. Dimension tables store and manage data (both numerical and nonnumerical) that flows through fact tables to form the data warehouse.

From a technical point of view, fact tables make note of numeric data related to various events. They could, for instance, include numeric values as well as foreign keys that map to additional (descriptive and nonnumerical) information in dimension tables. To get more analytical, fact tables keep a low level of granularity (or “detail”), which means they record information at a more atomic level. This could result in a large number of records being added to the fact table over time.

Data organizing in snowflake:

The snowflake schema normalises the dimension tables it connects with using this “snowflaking” method by (1) removing “low cardinality” attributes (that appear multiple times in the parent table); and (2) splitting the dimension tables into multiple tables until the dimension tables are completely normalised.

The snowflake database, like snowflake patterns in nature, becomes extremely complex. The schema can generate complex data relationships in which child tables have multiple parent tables.

Get ahead in your career with our Snowflake Tutorial !

2. Dimension table normalisation

The snowflake schema is a data structure that has been fully normalised. Separate dimensional tables are used to store dimensional hierarchies (such as city > country > region).Because it saves space, it can be used when the Dimension Table is relatively large.

Star schema dimensions, on the other hand, are denormalized. The repetition of the same values within a table is referred to as denormalization.It can be used when the Dimension Table contains fewer rows.

3. Redundancy in data

Snowflake schema fully normalizes dimension tables and avoids data redundancy, whereas star schema stores redundant data in dimension tables.Because the Snowflake Schema does have low data redundancy, it is cheaper to update and change.

A star schema, for example, would repeat the values in the field customer address country for each order from the same country.The Star Schema does have a high level of data redundancy, making it hard to maintain and modify.

The denormalization vs normalisation schema design causes redundancy, or duplicated entries.

4. Complexity of the query

A straightforward star schema relates to straightforward query creation. Analysts do not need to write multiple joins because the fact table is joined to only one level of dimensional tables.It is easy to understand  and has low query complexity.

Snowflake schemas, but on the other hand, necessitate a more complex query design. More joins are required to link the additional tables due to the complex relationships between the fact table and its dimensional tables. This adds to the overhead when writing analytical queries.

5. Performance of queries

Star schemas have a faster query execution time. Because dimensional tables require a single join between a fact and its set of attributes, a star schema functions almost as a single table for query lookups.

Snowflake schemas, on the other hand, necessitate complex joins of dimensional tables with their own sub-dimensional or supra-dimensional tables. This slows query processing and may have an impact on other OLAP products such as cube processing.

6. Hard drive space

Star schemas may run queries faster, but due to data redundancy, they require more storage space than snowflake schemas.

7. The integrity of data:

Star schemas put data integrity at greater risk than snowflake schemas. Because data is stored redundantly, multiple copies of the same data exist in the dimensional tables of the star schema. This means that new inserts, updates, or deletes can jeopardise data integrity.

The snowflake schema, on the other hand, is less vulnerable to data integrity issues because it fully normalises dimensional tables, storing dimension data only once in the appropriate table.

8. Installation and upkeep

Snowflake schema is a bottom up model.Star schemas are simpler to develop and implement. Since they are depicted by straightforward relationships, creating a suitable star schema is simple for a database developer or data architect.

Star schemas, but on the other hand, are more tough to sustain than snowflake schemas. Star schemas become more difficult to maintain and check for data integrity violations as new information is consumed into the data warehouse.Star schema is a top -down model.

Data Warehousing & ETLs, star-schema-vs-snowflake-schema-description-0, Data Warehousing & ETLs, star-schema-vs-snowflake-schema-description-1

Subscribe to our YouTube channel to get new updates..!

Benefits of star schema:

The following advantages are provided by star schemas:

  • Because all of the data connects through the fact table, the multiple dimension tables are treated as one large table of information, making queries simpler and easier to perform.
  • Easier reporting of business insights: Star schemas make it easier to pull business reports such as as-of-as and period-over-period reports.
  • Better-performing queries: By expelling the bottlenecks of a highly normalised schema, query speed and read-only command performance improve.
  • Data is provided to OLAP systems: Star schemas can be used to create OLAP cubes in OLAP (Online Analytical Processing) systems.

Top 30 frequently asked snowflake interview questions & answers for freshers & experienced professionals

Benefits of snowflake schema:

Snowflake schemas have the following advantages over standard star schemas:

  • Many OLAP database modelling tools are compatible with it: Certain OLAP database tools, such as those used by data scientists for data analysis and modelling, are particularly developed to function with snowflake data schemas.
  • Reduces the need for data storage: Normalizing data that would normally be denormalized in a star schema could indeed result in a significant reduction in disc space requirements. Largely, this is due to the fact that you are converting long strings of non-numerical data into numerical keys, which are significantly less taxing in terms of storage.

Challenges of snowflake schema:

There are three potential problems with snowflake schemas:

  • Snowflake schemas, as you could expect, add many levels of complexity while normalising the attributes of a star schema. As a result of this complexity, source query joins become more complicated. Snowflake’s ability to provide a more efficient way of storing data may result in performance degradation when browsing these complex joins. Nonetheless, advances in processing technology have resulted in improved snowflake schema query performance in recent years, which is one of the reasons why snowflake schemas are becoming more popular.
  • Slower cube information systems: Complex joins inside a snowflake schema result in slower cube data processing. In a broad sense, the star schema is preferable for cube data processing.
  • Low concentrations of data integrity: While snowflake schemas provide greater normalisation and fewer risks of data corruption after performing UPDATE and INSERT commands, they do not provide the level of transnational assurance that a traditional, highly-normalized database structure does. As a result, when loading data into a snowflake schema, it’s critical to be cautious and double-check the information’s quality after loading.

Snowflake Training

Weekday / Weekend Batches

Challenges faced by star schema:

Working to improve read queries as well as analysis in a star schema may present the following challenges:

  • Data integrity is compromised: Because of denormalized data structure, star schemas do not start enforcing data integrity quite well. Although star schemas employ steps to prevent anomalies from forming, a straightforward insert or update command could still result in data inconsistencies.
  • Database design creates and optimises star schemas for different analysis needs, making them less able to handle vast and varied queries. They work the best with a fairly narrow set of simple queries because they are denormalized data sets. A normalised schema, on the other hand, allows for a much broader range of more complex analytical queries.

Conclusion:

Which one of the two kinds of data warehouse schema will you be using?

Star schemas, on the other hand, are easier, running applications faster, and are simple to set up.Snowflake schemas, but on the other hand, are much less vulnerable to data integrity issues, are cheaper to update, and take up less space.

Premised on the tradeoffs discussed above, it really is up to you to determine which advantage (or disadvantage) better serves your company’s use situations.

Related Articles:



Source link