Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: rng primitive refactoring #3040

Open
wants to merge 19 commits into
base: main
Choose a base branch
from

Conversation

Alexandr-Solovev
Copy link
Contributor

@Alexandr-Solovev Alexandr-Solovev commented Jan 10, 2025

Description

Add a comprehensive description of proposed changes

List associated issue number(s) if exist(s): #6 (for example)

Documentation PR (if needed): #1340 (for example)

Benchmarks PR (if needed): IntelPython/scikit-learn_bench#155 (for example)


PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.

You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).

Checklist to comply with before moving PR from draft:

PR completeness and readability

  • I have reviewed my changes thoroughly before submitting this pull request.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
  • Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
  • I have added a respective label(s) to PR if I have a permission for that.
  • I have resolved any merge conflicts that might occur with the base branch.

Testing

  • I have run it locally and tested the changes extensively.
  • All CI jobs are green or I have provided justification why they aren't.
  • I have extended testing suite if new functionality was introduced in this PR.

Performance

  • I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
  • I have provided justification why performance has changed or why changes are not expected.
  • I have provided justification why quality metrics have changed or why changes are not expected.
  • I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev Alexandr-Solovev changed the title inc 1 feature: rng primitive refactoring Jan 22, 2025
@Alexandr-Solovev Alexandr-Solovev added the dpc++ Issue/PR related to DPC++ functionality label Jan 22, 2025
@Alexandr-Solovev Alexandr-Solovev marked this pull request as ready for review January 22, 2025 20:53
@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

Comment on lines 72 to 73
/// @param[in] queue The SYCL queue used to manage device operations.
/// @param[in] seed The initial seed for the random number generator. Defaults to `777`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please move those to the constructor's description.

Copy link
Contributor

Choose a reason for hiding this comment

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

It would be also good to provide the descriptions to every public method, not only to the class.

seed_(seed) {
engines_.reserve(count_);
for (Size i = 0; i < count_; ++i) {
engines_.push_back(dpc_engine<EngineType>(queue, seed_));
Copy link
Contributor

Choose a reason for hiding this comment

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

This initialization looks meaningless for mt2203. Because different engine_idx should also be provided to have independent sequences of random numbers:
https://www.intel.com/content/www/us/en/docs/onemkl/developer-reference-dpcpp/2023-0/oneapi-mkl-rng-mt2203.html

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

///
/// @tparam EngineType The RNG engine type to be used. Defaults to `engine_method::mt2203`.
///
/// @param[in] seed The initial seed for the random number generator. Defaults to `777`.
Copy link
Contributor

Choose a reason for hiding this comment

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

The came comment as for dpc_engine apply here: need to add descriptions to the methods and functions; need to fix rule of five.

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

1 similar comment
@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

Copy link
Contributor

@icfaust icfaust left a comment

Choose a reason for hiding this comment

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

This is a review just for the DAAL side of things, will do a second review for the DAL side. DAAL looks rather straightforward, and looks as though oneDAL requires the most attention.

@@ -0,0 +1,183 @@
/* file: mrg32k3a.h */
/*******************************************************************************
* Copyright contributors to the oneDAL project
Copy link
Contributor

Choose a reason for hiding this comment

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

The files in cpp/daal/include/* seems to follow exactly the layout of the other RNG engines, so I have glanced through to make sure that they are the same, but didn't look super close. @Alexandr-Solovev let me know if there is anything specific to mrg32k3a or philox4x32x10 in these folders that are different. This implies that there isn't any architectural change to the RNG engines on the DAAL side of things outside of the inclusion of the two new ones. Is that so? (on second glance, it looks that we are doing a better standardization of the error codes, but thats it?)

@@ -0,0 +1,60 @@
/* file: mrg32k3a.cpp */
Copy link
Contributor

Choose a reason for hiding this comment

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

Overall structure in the daal/src/* also looks to match. I will focus on reviewing the batch_impl.h files.

{
switch (technique)
{
case engines::internal::family: return false;
Copy link
Contributor

Choose a reason for hiding this comment

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

Not anything you need to change in your PR, but I find it a bit odd that all of the RNGs in DAAL define or try unused skipping methods entirely even if the technique isn't known to be implemented (i.e. false) rather than just setting the errorcode directly. Am I misunderstanding things?

@@ -19,8 +19,8 @@
// Declaration of template function that calculate mt2203s.
//--

#ifndef __MCG59_KERNEL_H__
Copy link
Contributor

Choose a reason for hiding this comment

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

This is crazy, especially for something that is so widely used in the codebase. Good catch.


#ifdef ONEDAL_DATA_PARALLEL

template <engine_type EngineType = engine_type::mt2203>
Copy link
Contributor

Choose a reason for hiding this comment

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

Will the change of default engine be left for a different PR?

/// Constructor that initializes the mt2203 generator for use on the GPU.
/// @param[in] queue The SYCL queue to manage device operations.
/// @param[in] seed The initial seed for the generator.
gen_mt2203(sycl::queue queue, std::int64_t seed) : _gen(queue, seed, 0) {}
Copy link
Contributor

@Vika-F Vika-F Jan 31, 2025

Choose a reason for hiding this comment

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

One more parameter should be added to the constructor.
Because mt2203 is a set of 6024 Mersenne Twister RNGs.

Suggested change
gen_mt2203(sycl::queue queue, std::int64_t seed) : _gen(queue, seed, 0) {}
gen_mt2203(sycl::queue queue, std::int64_t seed, std::int64_t engine_idx = 0) : _gen(queue, seed, engine_idx) {}

Comment on lines 38 to 40
for (std::int64_t i = 0; i < count_; ++i) {
engines_.push_back(device_engine<EngineType>(queue, base_seed_ + i));
}
Copy link
Contributor

Choose a reason for hiding this comment

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

More correctly will be to initialize the collection with the different RNGs for mt2203:

Suggested change
for (std::int64_t i = 0; i < count_; ++i) {
engines_.push_back(device_engine<EngineType>(queue, base_seed_ + i));
}
if (EngineType == engine_type::mt2203)
{
for (std::int64_t i = 0; i < count_; ++i) {
engines_.push_back(device_engine<EngineType>(queue, base_seed_, i));
}
}
else
{
for (std::int64_t i = 0; i < count_; ++i) {
engines_.push_back(device_engine<EngineType>(queue, base_seed_ + i));
}
}

throw domain_error(dal::detail::error_messages::unsupported_data_type());
}
oneapi::mkl::rng::uniform<Type> distr(a, b);
auto event = generate_rng(distr, engine_, count, dst, deps);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not returning the event?
Skip ahead for CPU can be just moved upper in the code.

}
}

explicit host_engine(const daal::algorithms::engines::EnginePtr& eng) : host_engine_(eng) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I do not think that this is a proper fix to rule of three. Because a copy constructor should accept the object of the same type host_engine.

engine_.skip_ahead_cpu(count);
}

//Currently only CPU impl
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add more meaningful comments.
What is the buffer is not obvious, for example.

Suggested change
//Currently only CPU impl
/// Generates a sequence of uniformly distributed random numbers from the interval [a, b).
/// The numbers in the sequence do not repeat.
/// In current version the data generation is only available on CPU.
///
/// @tparam Type ...
///
/// @param queue ...

@Alexandr-Solovev
Copy link
Contributor Author

/intelci: run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dpc++ Issue/PR related to DPC++ functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants