Docs on Migrating to v2 from Nebulex.Adapters.Dist.Cluster about nebulex HOT 5 CLOSED

Hey! Yeah, I see it is not mentioned in the migration guide. But the adapter you want to use is Nebulex.Adapters.Partitioned (it replaces the old one Nebulex.Adapters.Dist).

from nebulex.

Correct, the ttl is in milliseconds.

from nebulex.

ok i will create an MR to the docs once i finish the migration.

On the other hand, also i do not see (and not even searching in the code of previous versions) a reference to what should generation_size be updated to. I see a reference from a comment of yours that leads my to infer it refers to the cache size, so it can be updated to max_size, right?

from nebulex.

Right, as you may have seen maybe, the Nebulex.Adapters.Partitioned uses a local backend adapter, which by default is Nebulex.Adapters.Local, so yes, you can configure the max cache size with the option :max_size, you will find it in the docs. A configuration example may look like this:

config :my_app, MyApp.PartitionedCache,
  primary: [
    gc_interval: :timer.hours(12),
    max_size: 1_000_000,
    allocated_memory: 2_000_000_000 # In case you want to set a memory limit too
  ]

Let me know if that helps, stay tuned, thanks!

from nebulex.

Hey, regarding this, the ttl unit option (of set/put) was moved from seconds to miliseconds, right?

from nebulex.