{"id":"07d0d23e-80e4-44bf-a504-fef3d91e74a4","arxiv_id":"2501.14823","paper_version":2,"verdict":"REJECT","confidence":"HIGH","novelty_score":2.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":8,"one_line_summary":"Using a linear per-gigabyte energy and cost model, the paper computes that processing 80% of workloads on edge devices yields roughly 62% energy and 75% cost savings, and labels those numbers as benefits of Hybrid Edge Cloud.","lead":"Hybrid edge cloud, which runs most tasks on phones, cars, and IoT devices instead of central data centers, could cut energy and cost by roughly 60 to 80 percent if local processing is as efficient as assumed. The paper is a simple spreadsheet-style model of that tradeoff, so the useful content is the assumptions and sensitivity, not measured savings.","discovery_kind":"extension","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The headline 75% agentic energy saving is not derived from the stated model: Eq. (3.2) with §2.2 constants gives 61.8% at 80% edge split; the 75% figure appears only after §6.1 silently swaps Et to 5 kWh/GB.","rationale":"The reader's weakest assumption identifies the same load-bearing concern: the per-GB energy constants are not empirically supported, and the paper itself contradicts them in Section 6.1 by assigning agentic workloads a 5 kWh/GB transmission energy while the model in Sections 2.2 and 4.1 uses 0.7 kWh/GB. I agree with the reader's REJECT verdict. The most specific and decisive version of the concern is that the headline '75% energy savings in agentic scenarios' does not follow from the paper's own equations and constants: a straightforward recomputation with the stated parameters yields 61.8% at the 80% edge split. The 75% figure only emerges after swapping in an unmeasured 5 kWh/GB transmission constant. This is not a matter of external disagreement with consensus; it is an internal inconsistency between the formal model and the reported headline. The paper's Monte Carlo simulation does not rescue the claim because it uses the same unvalidated constants and is normalized so that the Pareto shape parameter has essentially no effect on total savings. A sensitivity analysis over the energy constants would show that every headline number moves with the assumed parameters, reinforcing that the paper currently reports arithmetic consequences of assumptions rather than measured or robust findings. The reader's recommendation of REJECT is appropriate; the path to acceptance would require correcting the inconsistent transmission energy, adding real per-GB measurements or citations, and providing a sensitivity analysis over the full parameter range.","tokens_in":6707,"tokens_out":5154,"duration_ms":50213,"concrete_test":"Recompute the Section 6.1 agentic energy savings using Eq. (3.2) with the Section 2.2 constants (Et=0.7, Ec=1.5, El=0.5 kWh/GB, Pedge=0.8). If the result is 61.8% rather than 75%, the headline relies on an unstated 5 kWh/GB parameter absent from the formal model. Additionally, trace the 5 kWh/GB value to a specific measurement or dataset in refs. [11]–[15]; if no source supports it, the parameter swap is unsupported and the abstract overstates the model's findings.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim that HEC achieves 75% energy savings in agentic scenarios is not a consequence of the paper's formal model. With the constants stated in §2.2 and §4.1 (Et=0.7, Ec=1.5, El=0.5 kWh/GB) and the 80% edge split used throughout, Eq. (3.2) gives S_Energy = ((0.7+1.5-0.5)/(0.7+1.5)) × 0.8 = 61.8%, not 75%. The 75% figure is obtained in §6.1 only by silently changing the transmission energy for agentic workloads to 5 kWh/GB, a value that appears nowhere in the model, the tables, or the Monte Carlo simulation, and is not supported by any measurement or citation. Thus the abstract's agentic headline is a parameter substitution rather than a derived result. The same fragility affects the cost claim: SCost = (0.10+0.20-0.02)/(0.10+0.20) × Pedge = 0.933 × Pedge, so a cost reduction 'exceeding 80%' requires Pedge > 85.7%, a split never justified for agentic workloads. Because the headline numbers are arithmetic outputs of assumed constants, and because no sensitivity analysis or empirical per-GB energy or cost data is provided, the paper does not establish its central quantitative claim.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper develops a closed-form analytical model to compare the energy and cost of centralized cloud computing against a hybrid edge-cloud (HEC) architecture, where a fraction Pedge of each device's data volume is processed locally and the remainder is sent to the cloud. The model includes per-gigabyte energy costs for transmission, cloud processing, and local processing, as well as bandwidth, hosting, and software costs. The paper applies this model to traditional IoT workloads (2.4 GB/device/day) and to hypothetical agentic workloads (20 GB/device/day), and it reports Monte Carlo simulations over Pareto-distributed workload sizes. The central claims are that HEC achieves \"energy savings of up to 75% and cost reductions exceeding 80%, even in resource-intensive agentic scenarios,\" with per-device annual savings on the order of 10,000 kWh and $1,500.","tokens_in":7077,"tokens_out":8336,"duration_ms":70273,"significance":"The question of where to place computation is practically important, and the closed-form expressions in §3.2 (S_Energy and S_Cost) give a transparent way to compare architectures if the underlying parameters are known. The paper is also commendable for explicitly modeling agentic workloads, which are likely to grow. However, the manuscript's own numbers do not follow from its model: the 75% agentic energy saving is obtained only by changing the transmission-energy constant in §6.1, and the traditional-workload example in §4.1 is inconsistent with the formula. No sensitivity analysis or empirical data is provided for the per-GB energy and cost constants, which are the very parameters that determine the headline results. The Monte Carlo simulation varies workload sizes but not these constants, so it cannot be considered an independent validation. As presented, the paper demonstrates a simple algebraic relationship and then attaches unsupported numeric values to it.","major_comments":[{"comment":"The abstract's headline of 'energy savings of up to 75%' in agentic scenarios is not a consequence of the model presented. With the constants stated in §2.2 and §4.1 (Et = 0.7, Ec = 1.5, El = 0.5 kWh/GB) and the 80% edge split used throughout, Eq. (3.2) gives S_Energy = ((0.7+1.5-0.5)/(0.7+1.5)) × 0.8 = 61.8%. The 75% figure appears only in §6.1, where agentic workloads are assigned a transmission energy of 5 kWh/GB, a value that is not part of the model, the numerical tables, or the Monte Carlo simulation. The claim is therefore a parameter substitution, not a derived result.","section":"§6.1 vs §3.2"},{"comment":"The numerical example for traditional workloads is internally inconsistent with the model. Eq. (3.2) with 876 GB/year, Pedge=0.8, and the stated constants gives EHEC = 876 × (0.8×0.5 + 0.2×2.2) = 735.8 kWh/year and S_Energy = 61.8%, yet the text reports 674 kWh/year and 'approximately 65%.' No derivation is given for these alternative numbers. Similarly, §6.1 asserts that traditional workloads show energy savings 'as much as 80%,' which cannot occur under Eq. (3.2) even at Pedge=1, where the saving is bounded by (1.7/2.2) = 77.3%. These contradictions undermine confidence in the reported results.","section":"§4.1"},{"comment":"The claim of 'cost reductions exceeding 80%' is not established by the model. With Cb=0.10, Ch=0.20, Cs=0.02 $/GB, the cost saving formula gives S_Cost = (0.10+0.20-0.02)/(0.10+0.20) × Pedge = 0.9333 × Pedge. Achieving S_Cost > 0.80 therefore requires Pedge > 85.7%. The paper does not justify such a high edge split for agentic workloads; the Pareto argument in §3.1 addresses workload counts (70-90% lightweight), not data-volume fractions, and §6.2 provides only qualitative statements. The abstract's numeric cost claim is thus not supported by the stated model and assumptions.","section":"§3.2 and Abstract"},{"comment":"The Monte Carlo simulation does not validate the model's key parameters. It varies workload sizes according to Pareto distributions and varies the edge split, but it holds the per-GB energy and cost constants fixed at the §4.1 values. It therefore cannot test the 5 kWh/GB transmission energy that underlies the §6.1 agentic claim, nor can it reveal how sensitive the reported savings are to the base constants. The observation that the two Pareto shape parameters give 'almost identical' results is a consequence of normalizing to a fixed annual workload; it does not establish robustness. As reported, the simulation is a recapitulation of the algebraic formula, not an independent check.","section":"§5"},{"comment":"The three per-GB energy constants are load-bearing but unsupported. The text states that the values are 'based on studies published in' [11]-[15], but those references are general surveys (Masanet et al., Cisco Global Cloud Index, Akamai) and do not directly supply 0.7 kWh/GB for transmission, 1.5 kWh/GB for cloud computation, or 0.5 kWh/GB for local computation. The paper provides no measurement, no dataset, and no sensitivity analysis for these constants. Since the savings formula is linear in these parameters and the headline numbers scale directly with them, the manuscript's central quantitative conclusions rest on unverified inputs.","section":"§2.2"}],"minor_comments":[{"comment":"The variables Pedge and Pcloud are described as 'probabilities' but are used as fractions of data volume; state explicitly that they are deterministic split fractions satisfying Pedge + Pcloud = 1.","section":"§3.2"},{"comment":"Reference [15] is missing its URL ('Retrieved from , 2023'); several other references (e.g., [13]) mix nonstandard formats and would benefit from a consistent style.","section":"References"},{"comment":"Figures 1 and 2 are referenced but not included in the submitted text; please ensure all figures are embedded and legible.","section":"Figures"},{"comment":"Section 6.1 uses the phrase 'exponential scaling of data transmission costs,' but the model in §3.2 is linear in data volume; this should be reworded to avoid implying nonlinearity.","section":"§6.1"},{"comment":"The paper would benefit from an explicit limitations paragraph acknowledging that the quantitative results depend on assumed constants and that the Monte Carlo simulation does not vary those constants.","section":"Discussion"}],"recommendation":"reject","confidential_remarks":"The manuscript reads as a promotional white paper for the mimik platform, with repeated product references and a concluding claim that HEC is 'indispensable.' Beyond the technical flaws documented above, the lack of any empirical grounding makes it unsuitable for a journal publication. If the authors revise, they should remove the unsubstantiated 75%/80% claims and present a sensitivity analysis; but as it stands, the central quantitative claims are not credible. This may also be a scope misalignment if the target journal expects independent research."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Quick take: this is a transparent but unsupported back-of-envelope calculation. The formulas are correct, and the qualitative conclusion that edge processing saves bandwidth and energy is true. But the headline numbers are not consequences of the model. The 75% energy savings for agentic workloads appears only after Section 6.1 silently changes the transmission constant from 0.7 to 5 kWh/GB; the stated model with an 80% edge split gives 61.8%. Similarly, 'cost reductions exceeding 80%' requires an edge split above 85.7%, which the paper never justifies. Section 4.1 itself says agentic energy saving is about 62%, so the abstract contradicts the paper's own analysis.\n\nWhat's good: the algebra in Section 3.2 is right, the cost model is a reasonable first-order account, and the authors are upfront about many assumptions. The Pareto discussion and Monte Carlo simulation are, however, decorative: the savings formula depends only on the edge split and the per-GB constants, not on workload size distribution, which is why alpha=2 and alpha=3 give 'almost identical' results. That is not validation; it is the model having no dependence on the varied quantity.\n\nThe load-bearing problem is the constants. 0.7, 1.5, 0.5 kWh/GB and $0.10/$0.20/$0.02 per GB are asserted with citations but no measurements or sensitivity analysis. Since every headline number scales linearly with those constants, the paper's claims are arithmetic consequences of assumptions, not empirical findings. The agentic 20 GB/day figure also appears without a source. Self-citation to the author's platform is not itself a flaw, but the paper reads more like an industry white paper than a research contribution.\n\nWho it's for: someone wanting a simple illustrative example of edge/cloud energy tradeoffs might find the model useful. It is not a result that supports the strong claims in the abstract. I would desk reject it for a journal and not send it to referees. A serious revision would need real per-GB energy data, a sensitivity analysis over the constants, and a consistent set of numbers between the model and the abstract.\n\nRecommendation: reject; do not invite resubmission unless the empirical basis is added.","headline":"The paper's arithmetic is transparent but its headline savings numbers require swapping in different constants halfway through, so the quantitative claims don't follow from the stated model.","tokens_in":7574,"tokens_out":3215,"would_cite":false,"duration_ms":29328,"reading_group":"maybe","serious_thinker":"no","would_accept_peer_review":false},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"Hybrid Edge Cloud can cut energy by up to 75% and cost by more than 80% by processing most data locally; the benefit scales linearly with the edge split.","keywords":["hybrid edge cloud","edge computing","energy efficiency","cost reduction","Pareto workload distribution","agentic workloads","Monte Carlo simulation","device-first computing"],"falsifier":"Measure the real per-gigabyte energy for an end-to-end workload: transmitting data to a public cloud region, running inference on a typical cloud instance, and running the same inference on a current smartphone or edge NPU. If measured cloud-plus-transmission energy is not roughly three times local-processing energy, the claimed 62–75% energy savings at an 80% edge split will not reproduce.","tokens_in":6515,"feed_emoji":"⚡","tokens_out":13685,"duration_ms":118541,"temperature":0.7,"pith_summary":"This paper tries to establish that a hybrid edge-cloud architecture, processing most data locally on devices and sending only demanding tasks to cloud gateways, can cut both energy and cost by large margins relative to today's centralized-cloud model. Its headline claim is energy savings up to 75% and cost reductions exceeding 80%, even for data-hungry agentic workloads. The argument reduces the benefit to a pair of linear savings formulas driven by the fraction of data processed at the edge and by per-gigabyte energy and cost constants; the paper's concrete example at an 80% edge split shows about 65% energy and 75% cost savings for traditional 2.4 GB/day devices. The conclusion is that device-first processing is practical and essential for the next generation of AI agents, robotics, and autonomous systems.","feed_headline":"Hybrid edge cloud cuts energy up to 75%, cost up to 80%","feed_subtitle":"Why it matters: heavier AI workloads make per-device energy and cost savings even larger.","key_machinery":"The load-bearing object is the pair of linear savings identities $S_{Energy}=((E_t+E_c-E_l)/(E_t+E_c)) P_{edge}$ and $S_{Cost}=((C_b+C_h-C_s)/(C_b+C_h)) P_{edge}$, together with the assumed per-GB constants. These identities convert a workload-allocation policy, the edge split $P_{edge}$, directly into percentage savings, so the benefit computation is a single multiplication rather than a simulation outcome. The Pareto workload distribution with $\\alpha=2$ and $x_m=1$ supplies the justification that 70–90% of workloads are lightweight enough to run locally, and Monte Carlo draws over that distribution (with $\\alpha=2$ and $\\alpha=3$) are used to confirm that the closed-form savings hold across edge splits from 50% to 90%.","core_discovery":"The central claim is that Hybrid Edge Cloud has a closed-form benefit law. If $P_{edge}$ is the fraction of workload data processed locally, energy savings are $((E_t+E_c-E_l)/(E_t+E_c)) P_{edge}$ and cost savings are $((C_b+C_h-C_s)/(C_b+C_h)) P_{edge}$, where $E_t$, $E_c$, and $E_l$ are the per-GB energy for transmission, cloud processing, and local processing, and $C_b$, $C_h$, and $C_s$ are the per-GB bandwidth, hosting, and software costs. Plugging in the paper's values, $E_t=0.7$, $E_c=1.5$, $E_l=0.5$ kWh/GB and $C_b=0.10$, $C_h=0.20$, $C_s=0.02$ dollars/GB, an 80% edge split produces about 62–65% energy savings and about 75% cost savings for traditional workloads. For agentic workloads generating 20 GB/day, the paper reports per-device savings around 10,000 kWh and $1,500 per year, with a separate agentic accounting reaching up to 75% energy savings.","pith_inferences":["Extension: Because the savings formulas are linear in $P_{edge}$ and independent of total data volume, the same percentage benefit applies across device classes, with only the absolute savings scaling.","Extension: The headline numbers can be tested directly by measuring the three per-GB energy constants on a real fleet and recomputing the formulas; any difference between measured and assumed constants changes the claimed savings proportionally.","Extension: The multi-trillion-dollar aggregate estimate assumes per-device savings multiply across tens of billions of devices with no added fleet-level coordination, cooling, or network costs, so a full-system accounting would need to add those terms."],"forward_implications":["An 80% edge split delivers roughly 65% energy savings and 75% cost savings for traditional workloads, matching the abstract's headline benefit range.","Agentic workloads at 20 GB/day yield similar percentage savings but roughly an order of magnitude larger absolute savings: about 10,000 kWh and $1,500 per device per year.","Even a 30% edge split gives 25–30% savings, so partial or incremental adoption is economically worthwhile.","At billions of devices, aggregate savings would reach tens of trillions of kWh and trillions of dollars annually, according to the paper's extrapolation."],"supporting_citations":[{"why":"Supplies the data-center energy-use recalibration behind the transmission/cloud energy constants.","marker":"[11]"},{"why":"Supplies the IoT/edge energy comparison used to set the edge-vs-cloud processing gap.","marker":"[12]"},{"why":"Cited as one basis for the cloud processing energy per GB figure.","marker":"[13]"},{"why":"Cited as one basis for the cloud processing energy per GB figure.","marker":"[14]"},{"why":"Cited as one basis for the cloud processing energy per GB figure.","marker":"[15]"},{"why":"Supplies the bandwidth cost range that anchors the $0.10/GB assumption.","marker":"[16]"},{"why":"Supplies the cloud hosting cost data used for the $0.20/GB assumption.","marker":"[17]"},{"why":"Documents the Pareto-style workload pattern that justifies the edge-split assumption.","marker":"[4]"},{"why":"Demonstrates a compact inference model running on resource-limited devices, supporting the feasibility of local processing.","marker":"[24]"}],"fun_headline_variants":["Hybrid edge cloud saves up to 75% energy, 80% cost","Edge cloud hybrid: 75% energy savings, 80% cost savings","Agentic workloads see up to 75% energy cut with hybrid edge","Hybrid edge cloud cuts energy 75%, costs 80%","Hybrid edge beats centralized: 75% energy, 80% cost savings"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The entire savings calculation rests on the assumed per-gigabyte energy figures—0.7 kWh for transmission, 1.5 kWh for cloud processing, and 0.5 kWh for local processing—and on those figures holding across workload types, even though the paper's agentic section adopts a different transmission value (5 kWh/GB).","fun_headline_variants_meta":{"raw":{"variants":["Hybrid edge cloud saves up to 75% energy, 80% cost","Edge cloud hybrid: 75% energy savings, 80% cost savings","Agentic workloads see up to 75% energy cut with hybrid edge","Hybrid edge cloud cuts energy 75%, costs 80%","Hybrid edge beats centralized: 75% energy, 80% cost savings"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000519,"raw_usage":{"total_tokens":2515,"prompt_tokens":949,"completion_tokens":1566,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":565,"completion_tokens_details":{"reasoning_tokens":1466}},"tokens_in":565,"tokens_out":1566,"duration_ms":13278,"temperature":1.0,"reasoning_tokens":1466,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-10T17:23:37.854678+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Measure the real per-gigabyte energy for an end-to-end workload: transmitting data to a public cloud region, running inference on a typical cloud instance, and running the same inference on a current smartphone or edge NPU. If measured cloud-plus-transmission energy is not roughly three times local-processing energy, the claimed 62–75% energy savings at an 80% edge split will not reproduce.","supporting_citations":[{"cited_title":"Aws pricing overview","cited_arxiv_id":null,"evidence_quote":"Cited as one basis for the cloud processing energy per GB figure."},{"cited_title":"Google cloud pricing","cited_arxiv_id":null,"evidence_quote":"Supplies the bandwidth cost range that anchors the $0.10/GB assumption."},{"cited_title":"Azure pricing overview","cited_arxiv_id":null,"evidence_quote":"Supplies the cloud hosting cost data used for the $0.20/GB assumption."},{"cited_title":"Barroso, J","cited_arxiv_id":null,"evidence_quote":"Documents the Pareto-style workload pattern that justifies the edge-split assumption."},{"cited_title":"State of the internet report","cited_arxiv_id":null,"evidence_quote":"Cited as one basis for the cloud processing energy per GB figure."},{"cited_title":"Cisco global cloud index: Forecast and methodology, 2020–2025","cited_arxiv_id":null,"evidence_quote":"Cited as one basis for the cloud processing energy per GB figure."},{"cited_title":"Masanet, A","cited_arxiv_id":null,"evidence_quote":"Supplies the data-center energy-use recalibration behind the transmission/cloud energy constants."},{"cited_title":"Venkatesh, V","cited_arxiv_id":null,"evidence_quote":"Supplies the IoT/edge energy comparison used to set the edge-vs-cloud processing gap."}],"review_version":1}