You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This module is bricked. Switched from PInteger to PPosixTime and my benchmarks had a huge regression. The issue is that all the operations wrap and unwrap the data, this results in a ton of iData and unIData builtin calls, because each addition unwrapped each integer from data and then wraps the result. Instead we should have two definitions PosixTimeData and PosixTime or anything else so that this can be avoided and we can just keep it in the non-data encoded format until we want to go back to data encoding.
The text was updated successfully, but these errors were encountered:
Yes, I'm aware of this issue. We are going to remove PDataNewtype which was a big mistake. It made types more intuitive, but really obfuscated cost of construting and deconstructing data value
plutarch-plutus/plutarch-ledger-api/src/Plutarch/LedgerApi/V1/Time.hs
Lines 67 to 96 in 429d1b0
This module is bricked. Switched from
PInteger
toPPosixTime
and my benchmarks had a huge regression. The issue is that all the operations wrap and unwrap the data, this results in a ton ofiData
andunIData
builtin calls, because each addition unwrapped each integer from data and then wraps the result. Instead we should have two definitionsPosixTimeData
andPosixTime
or anything else so that this can be avoided and we can just keep it in the non-data encoded format until we want to go back to data encoding.The text was updated successfully, but these errors were encountered: