Skip to content

Conversation

@mflatt
Copy link
Member

@mflatt mflatt commented Nov 21, 2025

No description provided.

@gus-massa
Copy link

Line 413:

- From this graph we still see reasonable scaling up to four cores,
+ From this **table** we still see reasonable scaling up to four cores,

@rfindler
Copy link
Member

Line 413:

Thanks!

has concurrency, and the expectation for libraries to work with
threads does not change with the introduction of parallel threads.
Racket's semaphores, channels, and other synchronization constructs
work the same will parallel threads as concurrent threads. Even
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be work the same with (not “will ”)

@samth
Copy link
Member

samth commented Nov 21, 2025

Should the attached code files be included in this PR (as opposed to keeping them on the utah site)?

@mflatt
Copy link
Member Author

mflatt commented Nov 21, 2025

Should the attached code files be included in this PR (as opposed to keeping them on the utah site)?

That would be better, but I didn't figure out how to get raco frog to move them in place.

absolute time for the coroutine column in this table is more
than double the absolute time in the previous table, meaning
that we're not learning anything about parallelism with the
speed up in this table, but instead the cost of consulting

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
speed up in this table, but instead the cost of consulting
speed up in this column, but instead the cost of consulting

The x1.3 in this column is not interesting for parallelism, but the x4.0 in the next column is interesting for parallelism.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

parameters in smaller continuations vs the cost in larger
ones.

And, as expected futures now provide no speedup at all.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
And, as expected futures now provide no speedup at all.
And, as expected futures now provide no speedup at all.

Not very important: No text change, but I'd move it after the "parallel" column discussion, between lines 462 and 463.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

rfindler and others added 3 commits November 21, 2025 17:12
Try to draw back out that parallel threads are robust to language
features like parameters, particularly compared to futures, and try to
dwell less on the performance of parameters themselves.

Also, some commas and spacing.
@samth
Copy link
Member

samth commented Nov 22, 2025

It looks like the thing done elsewhere on our blog is to put things in the img/ directory and then refer to them by absolute path, although that doesn't work locally. Frog also supports a way to refer to the img/ directory but that is apparently not configured correctly for our blog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants