Transpose allocates 16 bytes

Open
  • Is something wrong?
#384 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
performance

Research direction

Start with the linked NLPModelsTest.jl issue #128, NLPModels.jl issue #499 discussion, and NLPModelsTest.jl pull request #129 to understand the observed allocation and current tracking. Reproduce the 16-byte allocation for transpose in LinearOperators.jl, then determine whether the issue is resolved without regressing the relevant behavior or benchmarks.

Written by the indexing model from the issue text.

Description

@tmigot @amontoison

See existing discussion in https://github.com/JuliaSmoothOptimizers/NLPModelsTest.jl/issues/128, https://github.com/JuliaSmoothOptimizers/NLPModels.jl/issues/499#issuecomment-3544208564

Stopped tracking it recently in NLPModels: https://github.com/JuliaSmoothOptimizers/NLPModelsTest.jl/pull/129

I think it's due to making the {Adjoint/Transpose/Conjugate}LinearOperator, which has one field. Maybe we should pre-allocate those when making LinearOperator?

Dominant language
Julia
Stars
214
Forks
46
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaSmoothOptimizers/LinearOperators.jl

All issues in JuliaSmoothOptimizers/LinearOperators.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.