tensorflow / tensorflow/recommenders
How does regularisation affect the training speed? I am getting X100 boost.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 300
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I am experimenting with the base model from tutorials.
I have noted that after adding tf.keras.regularizers.l2(0.05) ) to embeddings layer two things happen:
- Metrics start growing - understandable.
- Speed of trining becomes X50-100 times faster. Why can it happen?
One more thing I noted is that when I add a few Dense layers without any regularizers or add tf.keras.regularizers.l2(1) with big weight to embedding I am getting all accuracies Top1, Top3, ..., Top100 equal to 1, and loss is low and stable. What is happening in this case?
vocab = tf.keras.layers.experimental.preprocessing.StringLookup(vocabulary=vocabulary[slot_name])
embedding = tf.keras.layers.Embedding(vocab.vocabulary_size(), embedding_dim, embeddings_regularizer=tf.keras.regularizers.l2(0.05) )
inputs.append( tf.keras.Sequential([vocab,
embedding,
# tf.keras.layers.Dense(32, activation="relu"),
# tf.keras.layers.Dense(32, activation="relu"),
]) )
Image: growing lines on the top - experiments with regularisation. Others - without. top_100_categorical_accuracy

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the tutorial base model and compare the shown Embedding configuration with embeddings_regularizer=tf.keras.regularizers.l2(0.05), the larger regularizer, and the added Dense layers. Reproduce the training-speed and Top-k accuracy behavior, checking the available model and metric setup. Done means documenting the cause of the differing results and identifying whether the behavior is expected or indicates an issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100