stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.18 and js-ipfs 0.33 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Con
<gozala>
Hi Folks, Is ipfs-desktop supposed to make added files available ?
thomasanderson has quit [Ping timeout: 260 seconds]
<lidel>
gozala, it should, its just a thing UI on top of go-ipfs (note it is alpha-quality app at the moment, there should be a new release that makes it a lot more useful in following weeks, you can build from master until then)
<lidel>
*thin UI
<gozala>
lidel: content uploaded through UI doesn’t seems to be picked up by the gateway for some reason
<gozala>
lidel: is that something new release supposed to address ? I can try go-ipfs instead too
<gozala>
lidel: is apfs-desktop comes with bundled go-ipfs or delegates to one on the system ?
<gozala>
lidel: I just updated go-ipfs and things got picked up
toxync01 has joined #ipfs
<gozala>
not sure if that’s because of the update or just incidentally happened at the same time
<lidel>
gozala, it comes with bundled one, but should respect $IPFS_PATH and if you have $IPFS_PATH/api already it will use API defined by multiaddr in that file (default on unix is ~/.ipfs/api)
SmileRobot[m] has joined #ipfs
<lidel>
(at least the version from master)
ygrek has joined #ipfs
<gozala>
lidel: hmm I don’t have $IPFS_PATH setup nor there is ~/.ipfs/api
<gozala>
I’m also not sure what that supposed to be
<gozala>
lidel: I was just wondering if desktop was using an older version of go-ipfs that was on my system and whether that caused some incompatibility
<gozala>
actually I can test that out by adding new file :)
<gozala>
lidel: It takes 2-3 mins now which is much better
<lidel>
ideally wrap it in time command to see how long it takes (time curl https://...)
<gozala>
lidel: is that supposed to have CID of the thing I’m trying to preload ?
<lidel>
yup
<gozala>
lidel: it might be worth adding that to the optional diagnostics of the GUI
thomasanderson has joined #ipfs
<lidel>
yeah we should also look into improving that resolution time at public gateway
<lidel>
I suspect background preload calls could help a lot
<lidel>
(until go-ipfs/dht itself gets better at this)
thomasanderson has quit [Ping timeout: 250 seconds]
pecastro has quit [Ping timeout: 268 seconds]
<Swedneck>
my ipfs node is somehow using 1 gig of ram, any idea how to improve that?
<Swedneck>
connection highwater is like 300..
<postables[m]>
you can run it in lowpower mode i guess
<postables[m]>
1gig of ram really isnt that much tho lol
<Swedneck>
it is when it's on a 4GB vps
<Swedneck>
jesus christ ipfs is using 5GB on my other server
joseminao has joined #ipfs
joseminao has left #ipfs [#ipfs]
AndreasLutro8 has joined #ipfs
AndreasLutro8 has quit [Remote host closed the connection]
ygrek has quit [Ping timeout: 268 seconds]
thomasanderson has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
petroav has quit [Ping timeout: 250 seconds]
thomasanderson has quit [Ping timeout: 252 seconds]
_whitelogger has joined #ipfs
spinza has joined #ipfs
<mntr0[m]>
how does ipfs perform on a system w 512mb ram?
Papa__Alpaka has quit [Remote host closed the connection]
thomasanderson has joined #ipfs
graphene has quit [Remote host closed the connection]
cwahlers_ has joined #ipfs
graphene has joined #ipfs
cwahlers has quit [Ping timeout: 268 seconds]
thomasanderson has quit [Ping timeout: 250 seconds]
cwahlers has joined #ipfs
cwahlers_ has quit [Read error: Connection reset by peer]
<mntr0[m]>
it should be written to scale down to 128mb ram
woss_io has quit [Ping timeout: 250 seconds]
<anacrolix>
Is there a GitHub issue for memory usage?
heartmire has joined #ipfs
heartmire has quit [Remote host closed the connection]
pep7_ has joined #ipfs
pep7_ has quit [Client Quit]
thomasanderson has joined #ipfs
thomasanderson has quit [Remote host closed the connection]
thomasanderson has joined #ipfs
dexter0 has quit [Ping timeout: 252 seconds]
dexter0 has joined #ipfs
jacobheun has quit [Ping timeout: 252 seconds]
jacobheun has joined #ipfs
thomasanderson has quit [Remote host closed the connection]
<postables[m]>
128mb ram? what is this the 90s lmao
<postables[m]>
*edit:* ~~128mb ram? what is this the 90s lmao~~ -> 128mb ram? what is this the 90s lmao, i jest. but try running in low power mode
<postables[m]>
*edit:* ~~128mb ram? what is this the 90s lmao, i jest. but try running in low power mode~~ -> 128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional memory optimizations altering configs slightly
talpers has joined #ipfs
<postables[m]>
*edit:* ~~128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional memory optimizations altering configs slightly~~ -> 128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional memory optimizations altering configs slightly. you could try lowering peer count, decreasing your ipns settings,
<postables[m]>
your routing type, decreasing GC frequency
<postables[m]>
*edit:* ~~128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional memory optimizations altering configs slightly. you could try lowering peer count, decreasing your ipns settings, your routing type, decreasing GC frequency~~ -> 128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional
<postables[m]>
memory optimizations altering configs slightly. you could try lowering peer count, decreasing your ipns resolver cache settings, your routing type, decreasing GC frequency
<postables[m]>
*edit:* ~~128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some additional memory optimizations altering configs slightly. you could try lowering peer count, decreasing your ipns resolver cache settings, your routing type, decreasing GC frequency~~ -> 128mb ram? what is this the 90s lmao, i jest. but try running in low power mode you can probably also achieve some
<postables[m]>
additional memory optimizations altering configs slightly. you could try lowering peer count, decreasing your ipns resolver cache settings, your routing type (i believe dhtclient has decent memory usage decrease but that may not be applicable to all use-cases), decreasing GC frequency