Correct Way to Use Persistent Term

anthonyl

Have been trying to figure out the correct way to code and use a persistent term, and am stuck.

How do I assign a variable to a persistent term that I can access outside the module it was created in?
How would I write the following code?

def build_store do

setup Persistent Term variable here

stream CSV File. I’m ok with this part using File.stream!() and parsing using split
|> Stream.map(fn x → #Add to persistent term here# end) this bit has me stumped

end

#Once term is created
#How do I read it here from another module?

Any assistance will be greatly appreciated

15 comments

#persistent_term

1 6063 15

2019-12-02 17:05:26 UTC

Showing Posts 1 to 10

Show Best Posts
Show All (oldest first)
Show All (newest first)

kip

ex_cldr Core Team

:persistent_term is VM-wide storage - so accessible from any module. This can create a bit of a challenge for naming so I typically use {module_name, key} as keys for persistent term.

The other consideration is balancing between a persistent storage and an amount of copying. Therefore I find myself using :persistent term when I can flatten the structure somewhat. For example, instead of storing a full map, I store each key of the map (and its value) in :persistent_term.

So to your example: Any module can access :persistent_term so stream and store to your hearts content.

Post #1

anthonyl

Thx Kip.

Do you perhaps have a code sample of the correct use of persistent term? I have searched high and low and been unsuccessful in finding one.

Post #2

kip

ex_cldr Core Team

I don’t seem to have a good example immediately to hand. I do have an example, but arguably its not a good one. Anyway, you’re welcome to whatever value it may contribute:

Compile time determination to use :persistent_term if its available
The relevant macro that uses :persistent_term.

Really, its a very niche, almost experimental, use case to emit a logger warning only once. Probably not a good example, but the only one I have to hand at the moment.

Post #3

anthonyl

Thx Kip,

Those examples are actually quite helpful. Please confirm if my understanding is correct. You basically use it as follows:

Create a unique key with the structure: modulename_key e.g mynamestore_firstname, mynamestore_lastname, mypricestore_socks
Save your value as:
`
:persistent_term.put(“mynamestore_firstname”, “Mark”)
:persistent_term.put(“mynamestore_lastname”, “Johnson”)
:persistent_term.put(“mypricestore_socks”, “25.00”)
etc…
Then to access you use:

first_name = :persistent_term.get(“mynamestore_firstname”)
last_name = :persistent_term.get(“mynamestore_lastname”)
sock_price = first_name = :persistent_term.get(“mypricestore_socks”)

Is that correct?

Post #4

Nicd

Be sure to check out the performance implications of using persistent_term: persistent_term — OTP 29.0.2 (erts 17.0.2)

Namely updating and deleting terms may result in a global garbage collection pass that may or may not be acceptable on your use case.

Post #5

anthonyl

Thx Nicd,

Yes, that is a very important consideration. The use case is a global lookup table that is only read once from a csv file and never updated. I believe it is ok in this use case. Is that correct?

Post #6

Nicd

Yes AFAIK that would be a good use case for persistent_term.

Post #7

anthonyl

I have tried this code and it is not working:

defmodule LookupTable do

def build_lookup do

load_path = Path.join([".", "data", "lookup.csv"])


File.stream!(load_path,[:read, :utf8]) #Read File
|> Stream.map(&String.trim(&1)) #Trim Each Element
|> Stream.map(&String.split(&1, [","])) #Split at Delimiters
|> Stream.map(fn n -> :persistent_term.put(hd(n),tl(n)) end)
|> Enum.map(&IO.inspect(&1))

:persisent_term.get("global_name")

end

I get the following error:

** (UndefinedFunctionError) function :persisent_term.get/1
is undefined (module :persisent_term is not available)
:persisent_term.get(“global_name”)

Post #8