Ngone51 commented on a change in pull request #28053: [SPARK-29153][CORE]Add
ability to merge resource profiles within a stage with Stage Level Scheduling
URL: https://github.com/apache/spark/pull/28053#discussion_r399986788
##########
File path:
core/src/test/scala/org/apache/spark/resource/ResourceProfileManagerSuite.scala
##########
@@ -98,6 +98,36 @@ class ResourceProfileManagerSuite extends SparkFunSuite {
assert(error.contains("ResourceProfiles are only supported on YARN with
dynamic allocation"))
}
+ test("ResourceProfileManager has equivalent profile") {
+ val conf = new SparkConf().set(EXECUTOR_CORES, 4)
+ val rpmanager = new ResourceProfileManager(conf)
+ var rpAlreadyExist: Option[ResourceProfile] = None
+ val checkId = 500
+ for (i <- 1 to 1000) {
+ val rprofBuilder = new ResourceProfileBuilder()
+ val ereqs = new ExecutorResourceRequests()
+ ereqs.cores(i).memory("4g").memoryOverhead("2000m")
+ val treqs = new TaskResourceRequests()
+ treqs.cpus(i)
Review comment:
It's not related to this PR, but just wondering why we use different API
name between executor and task for cpu/cores. Maybe it's follow original confs?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
