Web Server Workload Characterization
Assignment 3 and 4, COMPSCI 315
Due: Refer to the deadline on Canvas; Submission via Canvas
1 Introduction
Internet traffic measurement involves collecting network data that can be analyzed for several purposes such
as traffic modeling, designing better network protocols, and traffic management. The growth in popularity
of Web in the 1990s resulted in researchers trying to characterize Web traffic. These research works have
utilized Web server logs to understand the workload characteristics of Web servers. The results of the
research has led to improving performance of Web applications, designing better caching and load balancing
techniques, and providing better user experience to clients, among other things [1, 3–5].
2 Web Server Access Logs
In this assignment, you will analyze one of two university Web server access logs [2]:
1. A campus-wide Web server at the University of Saskatchewan (UofS_access_log).
2. A department-level Web server at the University of Calgary (UofC_access_log).
The server access log contains information about all requests made to the server and the corresponding
server responses. The server log is in the fixed text-based Common Log Format and has the following syntax:
hostname - - [dd/mm/yyyy:hh:mm:ss time_zone] object response_code transfer_size
The hostname is the resolved name or IP address of the client making a request for an object stored on
the Web server. The following fields (- -) are usually empty, but may contain user-identifier information
such as username. The next field indicates the day and time the request was made along with the time zone.
The URL requested is noted in the object field. The response_code field indicates the HTTP response
code returned by the server. The transfer_size field records the bytes transferred by the server.
For example, the following is a line from the UofS_access_log:
imhotep.usask.ca - - [15/Sep/1995:16:02:09 -0600] "GET /changes.html HTTP/1.0" 200 1254
This line represents a request made by host imhotep.usask.ca on September 15, 1995 at 4:02:09 p.m.
The time zone is central time (GMT-0600). The host requested the HTML file called changes.html using
HTTP version 1.0. This request was successfully completed by the server as shown by the status code 200.
The server transferred 1254 bytes to the host imhotep.usask.ca.
Note the following about the datasets:
• UofS_access_log: This trace contains seven month’s worth of all HTTP requests to the university
Web server. The logs fully preserve the originating host and HTTP request. A local client is one
containing usask.ca in the hostname or an IP address with 128.233.X.X. All others are considered
remote clients. Timestamps have 1 second resolution.
1• UofC_access_log: This trace contains approximately one year’s worth of all HTTP requests to the
University of Calgary’s Department of Computer Science Web server. The hosts making requests to
the server have had their addresses removed to preserve privacy. Hosts are identified as either local
or remote where local is a host from the University of Calgary, and remote is a host from outside of
the University of Calgary domain. Paths have been removed. Files were numbered from 1 for the
first file encountered in the trace. Files retain the original file extension, so that the type of file can
be determined. Paths of the filenames have been removed. Modified filenames consist of two parts:
num.type, where num is a unique integer identifier, and type is the extension of the requested file.
Timestamps have 1 second resolution.
3 Web Server Workload Analysis
Choose one dataset you like and answer all questions:
1. Based on your learning of Internet measurements in this course answer the following questions:
(a) What measurement mechanism was used for the collection of the Web server logs? Active, Passive,
or both.
(b) What type of network were the measurements taken from? Edge network, core network, or both.
(c) What type of analysis techniques did you apply on the dataset to get the answers? Online, offline,
or both.
(d) Is analyzing server logs the only way to characterize the workload of a Web server? Why?
2. How many requests are made per day on average?
3. How many bytes were transferred during the entire log duration expressed in Megabytes (MB)?
4. What is the average number of bytes transferred per day expressed in MB per day?
5. Produce a breakdown of the server response codes expressed in percentage of the total number of
requests. Group the status code as follows: Successful, Not Modified, Found, Unsuccessful. A successful
response (status code: 200) means that the server received a request for a valid object (for which the
client has the necessary access privilege), the object was found, and returned successfully to the client.
A not modified response (status code: 304) means that the client already has a copy of the requested
object in its cache, wants to verify if the object is up-to-date, and the client is informed that the
object has not been modified at the server. A found response (status code: 302) results when the
requested object is known to be stored in a different location than the URL requested by the client.
The server responds with the new URL in this situation. A unsuccessful response (status code: 4XX
and 5XX) happens when the requested object does not exist on the server, the client did not have
access permission, or there was a server-side error.
6. How many requests are made by local clients and remote clients, respectively? Report your answer as
a percentage of total requests.
7. How many bytes are transferred by local clients and remote clients, respectively? Report your answer
as a percentage of total bytes transferred.
8. Produce a breakdown of requests by file type category. The file categories are as follows: Video, Sound,
Dynamic, Formatted, HTML, Images, Others. Report your answer as a percentage of total requests.
The file categories by file extensions are described in Table 1.
9. Using Table 1, produce a breakdown of bytes transferred by each file category. Report your answer as
a percentage of total bytes transferred.
10. Using Table 1, calculate the average transfer sizes (in bytes) of each file category.
2Table 1: File categories
Category File extension
HTML html, htm, shtml, map
Images gif, jpeg, jpg, xbm, bmp, rgb, xpm
Sound au, snd, wav, mid, midi, lha, aif, aiff
Video mov, movie, avi, qt, mpeg, mpg
Formatted ps, eps, doc, dvi, txt
Dynamic cgi, pl, cgi-bin
Others Everything else
11. Identify all unique object requests in the log and sort them based on frequency. Next, identify all the
objects that were requested only once in the log. What percentage of unique objects are accessed only
once in the log? What percentage of bytes are accessed only once in the log?
12. Produce a Cumulative Distribution Function (CDF) plot of the transfer sizes of all distinct objects.
The x-axis should be in log-10 scale.
13. Produce at least one plot to show the percentage of total requests per hour of the day, the percentage
of total requests per day of the week, or percentage of total requests per month of the year.
14. Produce a CDF plot of the inter-reference times of objects that are requested more than once. The
x-axis should be in log-10 scale.
For questions 6 onwards, your analysis should be based on successful requests only. Report
your results to 2 decimal places. Some requests in the log may be malformed. It is safe to
ignore these requests in your analysis. Please check that these requests account for a negligible
fraction of the total requests. Briefly comment on your results (Explain the results and discuss
their implications).
4 Submission
Complete the attached file with your answers. Convert this file to PDF format. Rename it
to your username.pdf. Submit the file to Canvas. Submit answers to questions 1-7 as part of
Assignment 3. Submit answers to questions 8-14 as part of Assignment 4.
A code template will be provided at a later date. For added challenge, you are encouraged to write the
parser and analysis scripts from scratch using a programming language of your choice. You are free to use
online resources (e.g., online code, tools) as long as you provide appropriate attribution. You do not need
to submit the code. You should keep the code, in case we wish to see it. You are encouraged to discuss the
assignment with each other, however, the code and the produced results must be done individually.
Questions regarding this assignment and code template should be directed to the course tutors.
5 Grading Scheme
Each question is worth 10 points. Assignment 3 is worth 70 points. Assignment 4 is worth 70 points. For
each question, you will receive full points for the correct answer. You will receive 50% points for an answer,
which is close to the correct answer. You will receive zero points for an answer that is far off from the correct
answer. Each answer should have a brief explanation to receive full marks.
References
[1] Martin Arlitt and Tai Jin, A Workload Characterization Study of the 1998 World Cup Web Site, IEEE
Network 14 (2000), no. 3.
3[2] Martin Arlitt and Carey Williamson, Internet Web Servers: Workload Characterization and Performance
Implications, IEEE/ACM Trans. Netw. 5 (1997), no. 5, 631–645.
[3] Leeann Bent, Michael Rabinovich, Geoffrey M. Voelker, and Zhen Xiao, Characterization of a Large Web
Site Population with Implications for Content Delivery, WWW 9 (2006), no. 4.
[4] Venkata Padmanabhan and Lili Qiu, The Content and Access Dynamics of a Busy Web Site: Findings
and Implications, Proc. ACM SIGCOMM, 2000.
[5] Weisong Shi, Y Wright, Eli Collins, and Vijay Karamcheti, Workload Characterization of a Personalized
Web Site and its Implications for Dynamic Content Caching, Proc. WCW, 2002.
相关推荐
同花顺API实战指南:从零搭建股票数据自动化采集系统
本文提供了一份详尽的同花顺API实战指南,手把手教你从零开始搭建股票数据自动化采集系统。内容涵盖API权限申请、Python环境配置、数据采集与存储脚本编写、自动化定时任务实现以及数据清洗等核心环节,旨在帮助量化交易与数据分析爱好者构建稳定可靠的数据源,解放双手,提升研究效率。
Web 版翻译者资料库
本项目是桌面版《翻译者资料库》的 Web 移植版,基于 Spring Boot 3.3、Thymeleaf、Bootstrap 5.3 与 MySQL 8.0 构建。它面向翻译写作提供资料、词汇、句库、文本工具、对照制作、查找、备份恢复及旧库迁移等功能,完整继承桌面版核心业务规则,支持一键启动与离线访问。
角谱迭代与傅里叶变换迭代算法(GS)的原理及其实例演示分析
角谱迭代与傅里叶变换迭代算法(GS)的原理及其实例演示分析 目前,迭代法和强度传输方程(TIE)法是两类典型的非干涉相位检索技术(Phase Retrieval,被称为相位恢复、相位检索、相位反演法、相位复原等)。迭代法中的经典算法是Gerchberg-Saxton(GS),随后,出现了包括错误减少算法(ER)、混合输入输出法(HIO)、梯度搜索算法、角谱迭代算法等改进算法。...
Jackson 序列化 / 反序列化注解 完整版笔记
Jackson 序列化 / 反序列化注解 完整版笔记
Unity Android构建报错:compileSdk 35兼容性五层定位法
Android构建中的compileSdk是编译时API目标版本,其升级并非孤立操作,而是触发JDK、Android Gradle Plugin(AGP)、NDK、targetSdk与Unity引擎版本之间强耦合校验的起点。当出现'using a newer Android Gradle plugin to use compileSdk = 35'类报错,本质是代际技术栈错配——例如AGP 7.1.3不识别compileSdk 35所需Java 17语法,或NDK 21与AGP 7.4的ABI规范冲突。该问
C#粘包和分包问题及解决方法
一:通过图解法来描述一下分包和粘包,这样客户更清晰直观的了解: 下面对上面的图进行解释: 1.正常情况:如果Socket Client 发送的数据包,在Socket Server端也是一个一个完整接收的,那个就不会出现粘包和分包情况,数据正常读取。 2.粘包情况:Socket Client发送的数据包,在客户端发送和服务器接收的情况下都有可能发送,因为客户端发送的数据都是发送的一个缓冲...
MCP 协议会成为前端 AI 工程的标准接口吗?
MCP(Model Context Protocol)正在成为连接 AI 模型与外部工具、数据源的一层通用协议。本文从 MCP 的核心机制出发,分析它在浏览器与前端工程中的落地边界,讨论它能否成为前端 AI 工程的标准接口,并给出当下更务实的架构选择建议。
osgEarth 球上显示地形数据库
osgEarth 球上显示地形数据库 本文展示了一种由DSM和DEM得到Osgb工程,并在osgEarth球上显示的方法。其中DSM、DOM到Osgb工程的转换由VPB(VirtualPlanetBuilder)来实现,并采用Model图层将Osgb工程在球上显示。 本文主要解决一下问题: VPB编译 VPB生成地形 地形在球上显示 目录 1 前言 2 VPB编译与使用 3 地形在osgEarth球上显示 内容 1 前言 VirtualPlanetBuilder是一个开源代码工具,用于根据
LangGraph 本地 build 频频翻车,最终在服务器跑通流式对话
先说结论:我本地那个,一次都没成功过。三次,三次,全挂在拉镜像上。而顺得像刚上过油。这就很像我高中那辆自行车:骑着能走,一上锁就坏。那天晚上我盯着终端里那行红字看了很久,想的不是技术方案,想的是——为什么同一个工具,可以一边让我觉得自己很行,一边让我觉得自己不太行。
037、有源钳位反激变换器(ACF)原理
文章摘要 有源钳位反激变换器(ACF)是一种克服常规反激电路漏感能量处理瓶颈的高效解决方案。文章从实际炸机案例切入,指出RCD钳位电路在高压、宽范围、高功率场景下的局限性。ACF通过增加钳位管和钳位电容,将漏感能量回收而非消耗,实现效率提升2-3%、精准电压钳位和更好EMI性能。文章详细解析了ACF四阶段工作过程、关键波形特征,并指出设计陷阱:漏感需保持1%-3%特定范围、钳位电容ESR要求严格、需专用控制IC支持互补驱动。最后给出实用调试建议,强调ACF适用于65W+功率场景,低压验证后再逐步升压的调试方
DeerFlow 系列教程 第十二篇 | Tools 工具体系——从内置工具到 MCP 扩展
文件此工具允许 Agent 在运行时创建新的自定义 Agent。@toolsoul: str, # SOUL.md 的完整内容description: str, # Agent 的一行描述创建流程从获取agent_name写入配置文件(包含 name 和 description)写入灵魂文件SOUL.md(定义 Agent 的人格和行为)更新中的错误回滚MCP(Model Context Protocol)是一种标准协议,允许 AI Agent 连接外部工具服务器。DeerFlow 通过。
带着小白学习-微服务-6 实战:网关
地址栏输入:http://localhost:8088/goods/index,这时候就不是到8100端口去调用了,而是8088直接通过路由转发,分别到nacos对应的goods对应的服务中区调用。** 可以看出,这里将前面已经正常运行的server-store子工程(库存服务,服务提供方),server-goods子工程(商品服务,服务消费方)。(1)uri: lb://store 代表要到nacos的注册中心的服务列表中找到服务名为store的微服务;,网关是做路由转发,不是服务调用;
学习STM32的CAN总线通信
在配置时,确保您启用了CAN总线功能。CAN节点是CAN总线上的一个设备,每个节点都有唯一的标识符。在CAN总线中,有两种类型的节点:CAN控制器和CAN外设。步骤2:配置CAN总线 在STM32CubeMX中,选择CAN总线模块并进行必要的配置。在CAN总线中,有两个重要的概念:CAN节点和CAN帧。步骤5:测试CAN总线通信 在成功编译和烧录代码后,您可以使用串口调试助手或其他CAN总线工具来测试CAN总线通信。步骤3:编写CAN总线通信代码 在项目的主代码文件中,我们将编写CAN总线通信的示例代码。
海外平台频繁弹验证?从 DNS、WebRTC 到浏览器指纹的环境异常排查清单
在运营多地区海外平台账号时,即使代理节点通畅、TCP 握手成功,仍可能遇到频繁人机验证、地区限制、播放失败等异常。核心结论是:这类问题往往不在网络传输层,而在浏览器环境参数与网络出口之间的逻辑自洽性。本文从 DNS 泄漏、WebRTC 穿透、时区与语言匹配、Canvas/WebGL 指纹、TLS 特征五个维度,给出一份可复现的环境异常排查清单,并对比个人手动配置与工程化环境管理方案的适用边界。适用于跨境运营、多账号运维团队。
TMS_WebGMaps_1.9.8.0_Full_Source
TMS_WebGMaps_1.9.8.0_Full_Source 全源码 delphi cbuilder
jdk-8u144-linux-x64.tar.gz.
该资源为搭建Linux系统Java环境用,资源的后缀为tar.gz格式的压缩包
智能问诊的流程
本文介绍基于FastAPI构建的医疗多Agent系统MediAgent,通过症状分析、诊断推理与治疗建议等模块协同,实现从问诊到报告生成的完整工作流。系统采用前后端分离架构,结合MySQL、RabbitMQ与Docker实现工程化部署,支持异步化验结果接入。虽当前状态暂存于内存,但已具备可扩展性,未来可通过Redis持久化、消息队列联动及医疗安全机制完善,应用于慢病管理、辅助决策等场景,推动AI在医疗流程中的落地应用。
复分析 阿尔福斯(Ahlfors) 第三版答案 英文
答案分为十章,有部分习题没有答案,全英文复分析阿尔福斯(Ahlfors) 第三版答案
SSD测试工程精通系列 17|TRIM与UNMAP洪峰下的GC竞争(命令风暴与后台任务调度)
本文深入探讨NVMe SSD在面临TRIM/UNMAP命令洪峰时,后台垃圾回收(GC)与前端IO的竞争机制。从协议解析、固件调度、硬件架构到物理层信号,全面剖析命令风暴对QoS和WAF的影响。结合Samsung、Micron、Kioxia等厂商实测数据与失效案例,提供从测试注入、仪器抓取到工程取舍的全链路验证方案,助力资深测试工程师攻克存储性能断崖难题。
android 蓝牙通讯demo
android 下蓝牙通讯demo,实现了发现蓝牙,使能蓝牙,通过蓝牙发送消息。
基于 YOLOv8 的森林火灾检测系统(Web 版)
本项目面向林区早期火情识别场景,使用YOLOv8完成火焰(Fire)与烟雾(Smoke)两类目标的检测模型训练,并以FastAPI构建 Web 检测平台,把模型能力封装为可直接登录使用的系统。平台除常规的图片、批量、视频、摄像头检测外,还提供同图多权重对比、数据集浏览与标注核对、模型热切换,以及把训练搬到网页上的能力:可在浏览器配置超参数发起真实训练,训练中在线调整学习率、查看进度与动态曲线,训练完成后下载产物或直接应用到检测。
HTML5 History API 详解:前端路由底层原理
pushState改 URL 不刷新popstate接浏览器导航服务端必须兜底 SPA 入口前端路由的本质不是“魔法”,而是:把「URL 字符串」变成「组件渲染函数」的映射表,再让浏览器历史栈和这张表保持同步。
身份验证漏洞专题(三):持久登录、密码重置与密码修改中的凭据绑定缺陷
密码登录与双因素认证是身份验证的主干流程,但一个完整的认证体系还依赖三类辅助机制:持久登录("记住我")、密码重置、密码修改。这三类机制的共同特征是:它们同样携带或验证凭据,同样直接决定认证状态的归属,但实现时获得的防护强度往往远低于登录页面本身。攻击者绕不开登录接口时,常常可以从这些辅助入口进入。
2026 年前端框架排行榜
前端框架是用于构建用户界面的工具集合,通过预设组件、网格系统和样式规范提升开发效率与可访问性。2026年主流框架包括:React(生态领先,适合全栈)、Next.js(SSR/SEO优化,主流选择)、Vue(学习友好,中小团队首选)、Angular(企业级稳定)、Svelte与Astro(性能突出)。趋势显示,服务端渲染、TypeScript、AI工具融合及轻量化成为关键方向。就业建议:优先学React+Next.js;追求易用选Vue;企业级项目可学Angular;追求极致性能可尝试Svelte或Astr
Vue 前端开发 AI 对话页面:流式消息渲染、文件上传
关键点是不能手动设置 Content-Type 为 multipart/form-data,必须由浏览器自动生成带有 boundary 的请求头,否则后端无法解析。思路:将对象序列化为 JSON 字符串,作为 FormData 的一个普通字段(如 formData.append(‘payload’, JSON.stringify(data))),后端接收该字段后再反序列化。若上传大文件(>10MB),需实现独立的分片上传接口,在提交对话前先获取文件 id 或 url,再随文本发送引用。移除输入框的禁用态;
前端要加密手机号,密钥却不能下发:一次一密的 ECDH + HKDF 方案(十六)
前端加密手机号需避免密钥暴露,采用ECDH协商临时密钥,结合HKDF派生并绑定协议上下文,使用AES-GCM实现认证加密。关键在于两端参数严格一致:曲线、编码格式、盐值与info字段逐字节相同。避免直接哈希共享秘密或日志泄露密钥,服务端返回临时公钥并签名,前端先验签再派生密钥,确保前向安全与防中间人攻击。最终密文结构包含公钥、nonce、密文与认证标签,支持自校验。
浏览器端素材压缩与上传实践:从 Canvas 到 WebCodecs 与 FFmpeg 回退
本文介绍浏览器端素材上传的完整处理链路,重点解决图片与视频超限问题。图片通过Canvas等比缩放与质量压缩,逐级优化至2MiB内;视频则优先使用WebCodecs硬件编码,结合分辨率降级、码率预算与FFmpeg WASM回退,确保在20MiB内完成转码。强调“先确认后处理”原则,避免无谓资源消耗,并通过多层能力检测保障兼容性与性能。核心思想:压缩成功 ≠ 上传成功,需独立校验。
Geejing WebBuilder AI SQL:一句话生成查询的完整链路与「生成不执行」边界
企业里真正卡住数据核对的,很少是「不会写 SQL」。更常见的是三件小事叠在一起:这张表到底叫什么、日期字段是 `DATE` 还是字符串、当前这套库分页该用 `LIMIT` 还是别的写法。一个熟手要先翻一遍表结构,生手干脆把需求丢给 DBA,一来一回半天就过去了。
从一次检测到持续验证,重新认识 Web 应用安全测试
围绕漏洞修复后再次出现的问题,结合 Burp Suite DAST 与 GraphQL 示例,解析周期检测、证据管理和整改复测的实现思路。
副队长ES6+教程(3)--解构赋值
解构赋值是JavaScript中高效提取数组、对象数据的语法,支持按位置(数组)或属性名(对象)匹配,可设置默认值、跳过元素、使用剩余运算符。在Vue开发中广泛用于解构props、响应式数据及函数参数,提升代码简洁性与可读性。掌握其规则与常见陷阱,能显著提高开发效率。
2424



被折叠的 条评论
为什么被折叠?



