V3 Backport [#10888]: Update message for to clarify that local CPU profile is generated (#10889)

* Update profiling message

* Add changeset

* Fix formatting

* Fix formatting in startup-profiling.test.ts

Co-Authored-By: [email protected] <[email protected]>

---------

Co-authored-by: lrapoport-cf <[email protected]>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: 3 people

.changeset/shaky-sheep-dress.md

@@ -0,0 +1,5 @@
+---
+"wrangler": patch
+---
+
+Clarify that `wrangler check startup` generates a local CPU profile

packages/wrangler/src/__tests__/startup-profiling.test.ts

@@ -23,7 +23,7 @@ describe("wrangler check startup", () => {
 		await runWrangler("check startup");
 
 		expect(std.out).toContain(
-			`CPU Profile written to worker-startup.cpuprofile`
+			`CPU Profile has been written to worker-startup.cpuprofile`
 		);
 
 		await expect(
@@ -37,7 +37,7 @@ describe("wrangler check startup", () => {
 		await runWrangler("check startup");
 
 		expect(std.out).toContain(
-			`CPU Profile written to worker-startup.cpuprofile`
+			`CPU Profile has been written to worker-startup.cpuprofile`
 		);
 
 		await expect(
@@ -50,7 +50,9 @@ describe("wrangler check startup", () => {
 
 		await runWrangler("check startup --outfile worker.cpuprofile");
 
-		expect(std.out).toContain(`CPU Profile written to worker.cpuprofile`);
+		expect(std.out).toContain(
+			`CPU Profile has been written to worker.cpuprofile`
+		);
 	});
 	test("--args passed through to deploy", async () => {
 		writeWranglerConfig({ main: "index.js" });
@@ -103,7 +105,7 @@ describe("wrangler check startup", () => {
 		expect(std.out).toContain(`Pages project detected`);
 
 		expect(std.out).toContain(
-			`CPU Profile written to worker-startup.cpuprofile`
+			`CPU Profile has been written to worker-startup.cpuprofile`
 		);
 
 		await expect(
@@ -135,7 +137,7 @@ describe("wrangler check startup", () => {
 		expect(std.out).toContain(`Pages project detected`);
 
 		expect(std.out).toContain(
-			`CPU Profile written to worker-startup.cpuprofile`
+			`CPU Profile has been written to worker-startup.cpuprofile`
 		);
 
 		await expect(

packages/wrangler/src/check/commands.ts

@@ -88,7 +88,13 @@ async function checkStartupHandler(
 	await writeFile(outfile, JSON.stringify(await cpuProfileResult));
 
 	log(
-		`CPU Profile written to ${outfile}. Load it into the Chrome DevTools profiler (or directly in VSCode) to view a flamegraph.`
+		[
+			`CPU Profile has been written to ${outfile}. Load it into the Chrome DevTools profiler (or directly in VSCode) to view a flamegraph.`,
+			"",
+			"Note that the CPU Profile was measured on your Worker running locally on your machine, which has a different CPU than when your Worker runs on Cloudflare.",
+			"",
+			"As such, CPU Profile can be used to understand where time is spent at startup, but the overall startup time in the profile should not be expected to exactly match what your Worker's startup time will be when deploying to Cloudflare.",
+		].join("\n")
 	);
 }