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
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
j

jimn

02/18/2020, 11:59 PM
If this is a jvm-specific codebase kotlin concurrency is probably going to underperform at transaction granularity dispatch. I started along the lines of similar table manipulation using threadlocals and CoroutineContext composition and had to back out any suspend code and treat the coroutinecontexts as non-concurrent set objects to get sensible profiler results.
my specific metric was to get function sizes down below escape analysis metrics and identify any potential concurrency wins for thread-based swim lanes. suspension appears to induce excessive context protection overheads which have large inline-challenging functions even on explicitly single-threaded code.
a

altavir

02/19/2020, 12:35 PM
Sorry, I've missed your comments. I did not add manipulation yet and I still think about how to better add it if add at all.
Yesterday we had a discussion with @Zelenyi about that and came to some decisions. The key difference of what I am doing to, say, python, is that tables are effectively immutable, so when you do any operation on columns, you are actually constructing a new table, which can reuse columns from the old table. I am not sure, that we actually have a valid case, when we change only some values in the table. I would welcome any examples.
j

jimn

02/19/2020, 12:38 PM
mutable tables seems unimportant in the usecases im familiar with. iiuc
a

altavir

02/19/2020, 12:39 PM
@jimn Could you elaborate about what do you mean by mutable tables. Do you mutate single valuse in columns, or the whole column?
j

jimn

02/19/2020, 12:42 PM
i'm working on a pandas replacement personally. i have in the past used pandas to mutate cell values, perhaps a column at a time, or to do search and replace, but authoring such a facility would open the door to heap objects and a main reason for replacing pandas
cell values [in a dataframe] ^
a

altavir

02/19/2020, 12:43 PM
I am not concerned about heap for now, since I am developing an interface, which could later wrap other implementations. And implementations are responsible for memory, not API.
Column mutation is possible at the moment, without violating immutability. You just create a new table, reusing unchanged columns. We can also add implementation specific mutation methods later.
I would welcome any suggestions about API.
j

jimn

02/19/2020, 12:48 PM
i'm relativevly happy with what i've got to solve python problems with kotlin, and arrived at an immutable view manipulation framework. I'm more dissapointed with kotlin libraries as a whole, the suspension overhead is a 3x the cost of doing an atomic data access as is the suspension/flow capture overheads. the base language is not bad but carrying the jdk collections is surely just to appease the jvm/android momentum
a

altavir

02/19/2020, 12:49 PM
If you have something ready, I can try to integrate it with my API and see how it works. Suspesion is a very powerful tool, but is should be used with care and understanding.
j

jimn

02/19/2020, 12:49 PM
while it's one thing to build a bulletproof memory model and give every possible data usecase some attention at a cost of technical debt i think the reality is that a dataframe application should rely on doing a transform and live a short brutal life guaranteed to be cleaned up at a process level
the input structuring is basic as is to be expected for a first cut. I don't know if this is anything more thana technology demo for the kotlin typealiasing capabilities tbh. i have soemthing that can scale up beyond where pandas dies, the premise is simplistic and portable to rust or c++ which makes sense as any significant expansion of scope with the lessons learned here.
a

altavir

02/19/2020, 12:53 PM
I am not sure that I can elaborate on that without actual problem background. It is obvious that you can't find a universally good solution. Thanks for the reference, I will look into it later
j

jimn

02/19/2020, 12:55 PM
i would say this usecase is most applicable for spark datasets on a diet.
i intended to test out y,x storage along with x,y as an orthogonal, to choose IO models appropriately, however kotlin and IO do not mix.
a

altavir

02/19/2020, 12:57 PM
kotlin and IO do not mix
I do not agree, but we discussed it already. There should be some problem deffinition to discuss it further.
j

jimn

02/19/2020, 12:59 PM
key point is great functional programming language, generous jvm optimization potential to smooth over fundamental awkward libraries, and bijection-centric design principals that can occupy typealias conveniences absent from java proper. using NIO.
a

altavir

02/19/2020, 1:06 PM
We already discussed it. And I can repeat that I belive that in many cases you need to read data differently, not use different tool. But, again, we need to discuss specific use cases.
j

jimn

02/19/2020, 1:16 PM
the codebase is foundational in orthogonal access patterns for tabular data. as a first cut, the parts that were most easily improved happened by removing kotlin libraries and coroutines.
i eliminated capture and suspension overhead. it looks like the simplest possible parralellization to utilize underutilized cores is going to be java streams with threads. simpler still is port to c++ since it is now single threaded code, and insert openmp pragmas on a few inner loops.
i have considered that now the tabular y,x code is solid, i can create a file per column and unify these across combined cursors. one of my benchmarks converts 2.8 millionx7 cells into 1100x9800 give or take. so the intermediary would be generating, and mmap handles for at least 9800 additional small files. at this point those files no longer need the mmap code, and i don't have small-file access driver code at this time, so, until i see a really burning issue i'm ok with the existing costs up front. adding a seperate writable device is the cheapest IO upgrade
when i compare fwf textual input io to binary NIO field input of the same data, there is a single noinline keyword on the reducer eliminating any gains from hitting a smaller binary file, i believe.
this code is likely as optimal as jvm kotlin is going to get without an elaborate queuing of io zones for for batching up partial clusters