https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
u

ursus

09/20/2021, 1:22 AM
If I have a rather large
Map<String, String>
(keyed labels of UI elements), which is created dynamically via fetching the labels from api -- so not statically with string literals. Does it make sense to implement a
Trie
or is this somehow optimized under the hood in jvm since
String
is so special? I remember faintly about string interning, but that only applies to string literals and deals with copies, right? It might be more memory efficient, however what about lookup? I believe there are native implementations of this inside when simply matching
Strings
, no? Also, turning unicode strings to char arrays won't work all that great?
c

crummy

09/20/2021, 1:28 AM
how large is "rather large"?
u

ursus

09/20/2021, 1:32 AM
okay its not really really large, about 600 keys, hwoever they mostly looked like this
"usage_weekly": "/ týždeň",
"used_1_data": "použitý",
"used_1_min": "prevolaná minúta",
"used_1_sms": "odoslaná správa",
"used_24_data": "použité",
"used_24_min": "prevolané minúty",
"used_24_sms": "odoslané správy",
"used_x_data": "použitých",
"used_x_min": "prevolaných minút",
"used_x_sms": "odoslaných správ",
so, trie could optimize the size
but my question mostly is since
Char
is a class in kotlin, I presume
charArrayOf('a', 'b', 'c')
creates 3 Char instances on heap; which I fear would nulify anything; as opposed to java where its just primitive ints
public class Char private constructor() : Comparable<Char> {
    public fun toInt(): Int
}
I dont even understand what is this, virtual method with no implementation in a concrete class, huh?
okay guess I all ask this one separate first, thanks!
c

crummy

09/20/2021, 2:27 AM
i don't know the answer to your questions but I think if your map is <10k entries, or even 100k I wouldn't worry. definitely measure before you optimize
☝️ 1
d

Didier Villevalois

09/20/2021, 5:51 AM
@ursus Hi! Everything is an object in Kotlin. This does not mean they are not handled as primitives under the hood on the JVM. For instance,
Char
is handled under the hood as
char
on the JVM. However, there are cases where the JVM uses boxes around those primitives. For instance,
List<Char>
boxes the characters but
CharArray
does not. Also,
String
are interned on the JVM. I can't say about the performance however. In general, the JVM is very good at optimizing standard patterns. You should not try to prematurely and manually optimize things.
☝️ 1
u

ursus

09/20/2021, 5:58 AM
yes but interning is for literals, isnt it?
e

ephemient

09/20/2021, 7:46 AM
JVM string constants are automatically in the intern pool. strings can be manually interned, and there are some cases where it may make sense - e.g. if you expect to be re-constructing the same string repeatedly - but in practice the string pool is a fixed size hashmap, so make sure to have a realistic system benchmark before you consider interning strings (it may affect other code unexpectedly due to contention or eviction)
☝️ 1
as for a trie, it depends... for most cases I would expect the complexity wouldn't be worthwhile even if it did save memory, which isn't a guarantee - if you don't implement trie compression, or if you do but there are many short branches, you'll end up with a lot of object overhead for the tree nodes. have a realistic benchmark to measure before you commit to a trie.
u

ursus

09/20/2021, 12:45 PM
Yea I was worried about that node representation, even though hashmap has those entry objects, but this would require object per char; guess value types cant come soon enough
e

ephemient

09/20/2021, 5:15 PM
even if there were value types, an uncompressed trie is very wasteful. 12-byte object header + 16-bit char key + 32- or 64-bit pointer to data + padding = 32 or 40 bytes per character, while modern JVM String uses compact strings and can usually be 1 byte per character
u

ursus

09/20/2021, 7:56 PM
yes that was kind of the reason i posted here, i expected jvm string to be heavily optimized, unless there is some trick with primitive arrays to store not pointer but index of next one etc btw whats a compressed trie? compressed where, memory? disc?
e

ephemient

09/20/2021, 8:28 PM
for a set {"abc1", "abc2"}, a compressed trie is {"abc" => {"1", "2"}} instead of {'a' => {'b' => {'c' => {'1', '2'}}}}
🤔 1
u

ursus

09/20/2021, 10:32 PM
I see, thanks!