Quality of Service Performance Analysis of URL-to-Google Drive Transfer: Colab Runtime Versus Browser Local Transit

URL-to-Google Drive transfer via a browser may be inefficient because the file must pass through the local client twice: first during download, then during upload. This study evaluates the Quality of Service (QoS) performance of two transfer architectures: browser local transit and Google Colab runtime transfer. The browser local transit method is defined as a two-stage workflow in which a 100 MB file is downloaded from a URL to local storage using Google Chrome and then uploaded to Google Drive. The Colab method executes the transfer within a cloud runtime, while the local computer serves as the control interface. Each method was tested in five repeated trials under the same cellular hotspot environment. The measured parameters included active transfer duration, payload throughput, local traffic consumption, local quota efficiency, checksum validation, and statistical significance. The browser method recorded an average duration of 233.693 seconds, throughput of 0.429 MB/s, and local traffic of 211.365 MB. The Colab method completed the transfer in 4.830 seconds, achieved 20.841 MB/s, and consumed only 0.610 MB of local traffic. The Colab method reduced time by 97.933% and local traffic by 99.711%.