Update spark-compute.md

[zincob]

Spark VCores in the text is mentioned as 128 but in the table is 384. Table have been updated with 128

Thank you for contributing to Microsoft Fabric documentation

Fill out these items before submitting your pull request:

If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.

Not Applicable

Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.

Not sure

For internal Microsoft contributors, check off these quality control items as you go

Not applicable

Merge and publish

• After you #sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.
• The review team will use the comments section in the PR to provide feedback if changes are needed. Address any blocking issues and sign off again to request another review.
• Once all feedback is resolved, you can #sign-off again. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).
• From the main branch, the change is merged into the live branch several times a day to publish it to the public learn.microsoft.com site.

[prmerger-automator]

@zincob : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 27c9194:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/data-engineering/spark-compute.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ShannonLeavitt]

@santhoshravindran7

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[zincob]

Is there any update? Documentation is still unclear and providing 2 different information

[zincob]

The documentation is extremely confusing.
Spark Compute: Here the text says "SKU F64 has 64 capacity units, which is equivalent to 128 Spark VCores." there is no reference at all the Burst and then the table out of the blue mentions 384 VCore

Spark Job Concurrency: Here the Burst factor for F64 is 3.

Burstable Capacity: Here Burstable scale factor is 1-12x. True that this is referring to the warehousing but it makes everything quite confusing.

[santhoshravindran7]

thanks for the feedback
will it help i change the column name to Max Spark VCores with Burst Factor
if we are adding the burst vcores along with spark vcores available

the bursting for spark is explained in the https://learn.microsoft.com/en-us/fabric/data-engineering/spark-job-concurrency-and-queueing

will add another column with the max burst so its more clear

[SnehaGunda]

@santhoshravindran7 can you reference your PR once you have it?