|
HEBench
|
The operation for this workload is the logistic regression with sigmoid activation function.
This operation is defined as:
where
Input: 3 parameters
| Parameter | Description |
|---|---|
0 | W is the feature vector for the linear regression with n features (number of components in the vector). |
1 | b is the bias for the linear regression. This is a scalar. |
2 | X is the input vector to the linear regression. It has n components. |
Output: 1 output
| Output | Description |
|---|---|
0 | P(X) is a scalar. It is the result of the logistic regression. |
Given the feature vector W and the bias b, for any input vector X_
where:
is the result of the linear regression. X_ . W is the dot product between vectors X_ and W, and
is the standard sigmoid function.
This document applies to the following workloads:
For hebench:APIBridge::Workload::LogisticRegression_PolyD3, hebench:APIBridge::Workload::LogisticRegression_PolyD5, and hebench:APIBridge::Workload::LogisticRegression_PolyD7 the sigmoid activation is approximated around x = 0 using a polynomial. The polynomial approximation used is[1]:
Degree 3:
Degree 5:
Degree 7:
Required workload parameters: 1
| Index | Name | Type | Description |
|---|---|---|---|
0 | n | uint64_t | Number of features in feature vector W. This is the number of components for vectors W and X. |
Above parameters are required for the workload in the specified order. A backend must specify, at least, a set of default arguments for these parameters.
Backends can require extra parameters beyond the base requirements. If a backend requires extra parameters, these must have default values in every set of default arguments for the workload parameters.
This workload supports the following categories:
See Latency Category .
See Offline Category .
Value ranges for elements in CategoryParams::offline::data_count. Default value is used when the backend implementation sets the data_count for the corresponding operand to 0, but user specified 0 or no value at run-time.
| Parameter | Lower bound | Upper bound | Default |
|---|---|---|---|
0* | 1 | 1 | 1 |
1* | 1 | 1 | 1 |
2 | 1 | none | 100 |
* When set to 0, these are set to the specified default values. Not affected by Test Harness sample size option.
This workload is defined for the following data types:
All scalar elements in a vector with elements of type T (where T is any of the supported types) lie contiguous in memory.
For example, given the following vector A with n = 3 components:
The elements will be stored in memory as:
| Offset: | 0 | 1 | 2 |
|---|---|---|---|
| A | a0 | a1 | a2 |
Backends should expect this layout for their raw, clear text inputs, and must generate this layout for their decoded outputs.
If several vectors will be pointed at by a single pointer, consecutive vectors will follow each other in memory.
All scalars will be represented as vectors with a single element.
Supported modes:
| Generate | External |
|---|---|
| yes | yes |
Data generation for vectors used as input for this workload occurs during workload initialization by Test Harness. Ground truths are pre-computed during data generation. There is no standard dataset.
During data generation, all vector elements are extracted from a pseudo-random normal distribution of mean 0 and standard deviation of 1: n(0, 1).
[1] - M. Kim, et al. "Secure Logistic Regression Based on Homomorphic Encryption: Design and Evaluation" Cryptology ePrint Archive, Report 2018/074, 2018.