Vector is thread-safe, ArrayList is not, but ArrayList is faster. You can wrap it in a synchronisedList to get thread safety on ArrayList. That's the video condensed. You're welcome
Well they realised that synchronising things by default was a bad design choice as A) there was a performance cost to synchronisation as it stops the JVM fro m doing certain optimisations, and users should not may the cost of hey are notneeding concurrent access. B) if concurrency was required, you would probably need to synchronise the calling code anyway, to allow read and modify ops to be atomic, so no point syncronsing the list operations. You can see this in stringBuilder vs StringBuffer
I've been longing for you to publish a new video, and each time I'm fascinated by them regarding presentation technique, confidence and knowledge gain. This video - among all others you've produced - will be added to the "interesting video list" of my computer science class here in Germany. Thanks for making these kinds of videos.
I started working with Java back in 2001 and one of the first things I learned was Vectors were a big no-no, but nobody bothered to explain why. Many years later you showed us the reasons, so thanks!
I ❤coding with you John! I coded with Vector and then migrated to ArrayList, I knew about thread safe, but only in theory. Your class was fantastic for me to understand how this works in practice. Congratulations.
I used vectors in C++ for years. I had no idea that Java had vectors. I shall continue using ArrayLists, as you instructed us. Thank you, Coding With John. Awesome explanation and demonstration, as always.
Hi John I really appreciate the effort you put into explaining Java topics with such simplicity. The first video I watched was on Optionals and it finally made sense why they were introduced in the first place. Can you please make a video on Java Functional Interface, Consumer, Predicate and Supplier?
I think they modelled the early Java on C++, which is why they used the same names. However they made a design error in making vector synchronised as you pay a high cost to it being synchronised, and also most ops require synchronisation at a higher level. They could not fix the design errors without breaking backward compatibility, so they created ArrayList instead
i have never heard of vectors lol, now I feel like I have a much better understanding of them. thanks for explaining the concept in such a clear and engaging way, seriously you are the only education youtuber that i watch his contents not because i have to but i want to, so fun to watch and not boring at all ♥ unlike many educational youtubers, can't wait for the next video keep up the great work! ♥(we miss the smile)
Great video, in my case for some reason the Vector was faster than the ArrayList form some reason!! But now I know how to use them! Great video thanks.
I want to buy your course but I have been with Java for some time now. Thus, I would 100% be buying your Advanced Java course which includes advanced contents just like how you do it in this Channel.
Can someone please explain, why do I get the same results for both ArrayList and Vector? I am not using any wrappers, I am jsut running the same code as John, and yet my ArrayLists are not in any way faster than my Vectors, why is that? Am I using a wrong JRE or something? Maybe there is something to do with Maven? For example, I get this: Added 10000000 elements to ArrayList: 251ms Added 10000000 elements to Vector: 242ms Added 10000000 elements in a multithreaded way to ArrayList: 1030ms Added 10000000 elements in a multithreaded way to Vector: 1275ms
Hi! Nice video. When I was working with JTable I always extending AbstractTableModel using ArrayList because I believed that the DefaultTableModel was deprecated for use Vectors. But Vectors are still around here as DefaulTableModel too. Thanks John and sorry for my english..
With the vector both add and get methods are synchronized. You might have a case where you build a list once, and then want to READ from it from multiple threads. That should be safe with just the unsynchronized ArrayList, but to be safer you could wrap the list in an Collections.unmodifiableList. Then you won't need the overhead of synchronization on your get calls.
Very interesting video. I used Vectors way back in 1.2 or 1.3 but never bothered to find out how they are different than ArrayList. Thank you. Keep up the good work.
SIRRRRRR......U R Great... you solved my longlasting issue by vector class. i was making a 2d style java game and usling LinkedList. when i skip level or in fast or sometime it stuck it always gave me error. linkedlist. it tried above code for sync, but did not work. after watching your video, i changed it to vector . no issue now, no significant or noticable lagg or any issue that was facing and hitting head with codes and its technique OOP method. Great.......
You can used synchronized in one of the threads. This synchronises in both threads which might not be necessary when there are 2 threads. N threads N - 1 synchronisations. If N is large you can synchronize all threads.
Great video. One suggestion I would give is to use Duration to measure time instead of System.currentTimeMillis() as it is not that reliable, specially when dealing with lots of data, the effect of CPU throttling and time leap will mess your count. LocalDateTime with duration to measure the difference is better
Whole video summarized in a sentence: Vectors are slower because unlike arraylists they are thread-safe so just use arraylists and if you have multiple threads use Collections.synchronizedList(arrayList).
Funny Thing is if i switch the first example around, adding to the vector is faster than adding to the arraylist. Checked again with two ArrayLists and adding to the first datatype is always half the time than adding to the second one ^^
Thanks for sharing about vectors asd arraylist , you demonstrated how arrayList performs poorly with multi threads if not synchronised. what happens if parallelStreams are used? Does it automatically gets wrapped into Collections.synchronized()
no idea if it has been covered, but explaining public, private, protected and package private might be a good idea. just a thought. and in my opinion making some examples a little bit more complex might help for like a real world example. as extending some functionality might be tricky for learning developers. also if possible, please stick to one IDE swapping between intelli J and Eclipse can be mildly distracting. and an ide specific functionality is a pain if someone is using Eclipse and they wanna do something only available in Intelli J other wise love your good work, very helpful could we have a lesson on FUNCTIONS, BIFUNCTIONS, SUPPLIERS, CONSUMERS and other functional interfaces with a demo of passing them to methods etc :)
I have a quick question regarding the performance difference between Vectors and Arraylists, or more specifically with the synchronizedlist, if you create the synched list wrapper for your arraylist, does it only take that performance hit and start behaving comparably to a Vector in a threaded environment, or does it slow down the ArrayList when accessing it in a single thread also?
Hello John, always appreciate your clear and concise way of explaining difficult JAVA concepts, can you please talk about Dynamic proxies when you get a chance? Thanks
Someone tell John we would really love an intro to springboot course from him, perhaps some 30 min crud app of some sorts. His videos helped me finally get the hang of recursion after reading hundreds of articles and numerous youtube videos later.
I saw weird behaviours when testing... I ran it with Java 20, and consistently Vector was faster than ArrayList with a milion item, but with 10, ArrayList is faster again...
Me Gusta :) Next video, maybe something about switch statement and how it evolved in Java? Or maybe something about using debugger in most popular IDE's? That would be also extremely useful for beginners :)
Hello John! Please post more videos!! When I watch your explanations I don’t feel like a complete idiot who can never be a developer but the opposite!!!! It would be cool if you made some videos about patterns of programming or about spring framework or about microservises Anyway whatever you do I love your content!)
Vectors in Java were initially implemented to be thread safe as the original philosophy in Java was to just do everything one way to fit every use case. It's the reason why every method is virtual and must be contained in a class, among other things. By the way, the other data structure from the original Java version is Hashtable. It corresponds to the more useful HashMap. It's also worth noting that Java also have a number of other concurrent data structures in the java.util.concurrent package, like BlockingDeque, ConcurrentHashMap, etc.
in javaFX Application is an abstract class. In this abstract class there have some abstract methods which are overridden in main class which extends abstract Application class and also have static launch() method in abstract class Application. The launch() method calls from the main method in main class. Now how is it possible launch() method calls these abstract methods and for these calls overridden methods in main class are executes? please help to understand
Hi there. Is there some news on the Vector Api? When they will exit the incubation state? I put a lot of effort to use them in my program and they are devastating on some loads with CPUs that supports AVX512. My concern is that I'll need to rewrite everything for API changes when the APIs will exit the incubator state. I have some "development questions" on those APIs, are there a mailing list where to discuss about the use and the benefit of those APIs?
The thread experiment probably does not guarantee mutual exclusion and order of delivery, right? So, how does ArrayList and Vector behave on synchronized scenarios with semaphores, reentrant locks and so on... Also, in the beginning you just printed out the static 1M integer value instead of printing the Collection object's size, but still good video, very informative, thanks.
Haters gonna say the new updates are bad, but you can still use the old ones and also if you don't develop you will just get stuck in the past. I think most new things are optional and you don't have to use them, however it's always good to use both. I will continue to use the old hello world but I will also try out new things and learn the new update as well. Having additional knowlege will always give an advantage.
When using awt/swing parts of the api uses vector (probably because the api was written before the collections framework) and it's pretty annoying to be forced to use vectors in multiple places or copy a bunch of array lists into vectors.
I'm running this code locally and the elements are being added to a vector about 2x faster than an arrayList (consistently). Could this be because I'm on an M series Mac with ARM architecture?
Hello John I would like to see a real practical example of using the java collection framework. I never understood the fundamentals of collection framework and if it is related to the database like mysql. I am really struggling with the concept of database and data structures. Please help 😢 SOS
Hello and thank you. Should we use Vector if we are just reading from List in multithreading mode? Is ArrayList is safe for reading in multithreading? Thanks in advance!
If it’s only accessed from one thread you do not need to synchronise, and if it’s accessed from multiple threads you may want to handle the synchronisation in the surrounding code to allow several operations to be atomic. Alternatively there says there are constructs that are better suited to concurrency, such as a concurrent hash map
I've used Vectors in C++. Considering where I come from, where things are supposed to safe instead of just fast, I may keep using Vectors in Java. At least when I don't get punished by a boss for doing so.
Can you make a multi-threading video like one thread need to create a image in dir with distinct name and another side the thread need to write a text in one file upto 2 Million in efficient way
could've extracted the single-threaded and multi-threaded benchmarks into separate functions taking a List instead of copy-pasting and renaming variables all over the place
TLDR: Vectors are synchronized, thus thread-safe and slower. ArrayLists are not synchronized, thus faster, but unsuitable for multi-threaded scenarios.
The only other situation is if you're using 3rd party code, and they force you to use Vector. Of course, you'd try to limit the use of Vector by copying into a Vector at the very last minute just before passing it as a parameter. If a Vector is returned, it may be useful to just put it into a List variable if you're not going to manipulate the elements in any way afterwards. If you are, still put it in a List variable, but consider if you need the thread safety. If not, then copy from the Vector into an ArrayList.
By the way, you can add underscores to number literals to make them more readable:
int size = 1_000_000;
I never knew that and it looks so weird lol
jusr like in rust and js
@@v0xl and python :)
It works only with Java 11 and newer, but yeah you can.
You can do 1e6 too
Vector is thread-safe, ArrayList is not, but ArrayList is faster. You can wrap it in a synchronisedList to get thread safety on ArrayList. That's the video condensed. You're welcome
❤
ArrayList: "I'm fast at adding elements!"
John: "But you did not add of them in multithread call"
ArrayList: "I said I'm fast, not correct"
Well they realised that synchronising things by default was a bad design choice as
A) there was a performance cost to synchronisation as it stops the JVM fro m doing certain optimisations, and users should not may the cost of hey are notneeding concurrent access.
B) if concurrency was required, you would probably need to synchronise the calling code anyway, to allow read and modify ops to be atomic, so no point syncronsing the list operations.
You can see this in stringBuilder vs StringBuffer
That makes sense.
I've been longing for you to publish a new video, and each time I'm fascinated by them regarding presentation technique, confidence and knowledge gain. This video - among all others you've produced - will be added to the "interesting video list" of my computer science class here in Germany. Thanks for making these kinds of videos.
I started working with Java back in 2001 and one of the first things I learned was Vectors were a big no-no, but nobody bothered to explain why. Many years later you showed us the reasons, so thanks!
I ❤coding with you John! I coded with Vector and then migrated to ArrayList, I knew about thread safe, but only in theory. Your class was fantastic for me to understand how this works in practice. Congratulations.
I used vectors in C++ for years. I had no idea that Java had vectors. I shall continue using ArrayLists, as you instructed us. Thank you, Coding With John. Awesome explanation and demonstration, as always.
no way anyone goes emptyhanded from your videos ,there is always something to learn in deep..
thanks teacher.....
Hi John
I really appreciate the effort you put into explaining Java topics with such simplicity. The first video I watched was on Optionals and it finally made sense why they were introduced in the first place.
Can you please make a video on Java Functional Interface, Consumer, Predicate and Supplier?
Such an interesting video. I've used Vector in C++ but never knew it existed in Java too. Your videos are always so educational
C++ Vector = ArrayList in Java
The Power of C++ you can write any realization you need both threadsafe and none... With or without buffering and so on...
@@yuriytheone Yeah you can do all of that in Java too. Your point?
I think they modelled the early Java on C++, which is why they used the same names. However they made a design error in making vector synchronised as you pay a high cost to it being synchronised, and also most ops require synchronisation at a higher level.
They could not fix the design errors without breaking backward compatibility, so they created ArrayList instead
For the benachmarking, I'd keep the `new Thread` part outside of the timing - just time from before the starts to after the joins.
i have never heard of vectors lol, now I feel like I have a much better understanding of them. thanks for explaining the concept in such a clear and engaging way, seriously you are the only education youtuber that i watch his contents not because i have to but i want to, so fun to watch and not boring at all ♥ unlike many educational youtubers, can't wait for the next video keep up the great work! ♥(we miss the smile)
Laughs in c++
Great video, in my case for some reason the Vector was faster than the ArrayList form some reason!!
But now I know how to use them! Great video thanks.
I want to buy your course but I have been with Java for some time now.
Thus, I would 100% be buying your Advanced Java course which includes advanced contents just like how you do it in this Channel.
Finally a new video
Can someone please explain, why do I get the same results for both ArrayList and Vector? I am not using any wrappers, I am jsut running the same code as John, and yet my ArrayLists are not in any way faster than my Vectors, why is that? Am I using a wrong JRE or something? Maybe there is something to do with Maven?
For example, I get this:
Added 10000000 elements to ArrayList: 251ms
Added 10000000 elements to Vector: 242ms
Added 10000000 elements in a multithreaded way to ArrayList: 1030ms
Added 10000000 elements in a multithreaded way to Vector: 1275ms
Hi! Nice video. When I was working with JTable I always extending AbstractTableModel using ArrayList because I believed that the DefaultTableModel was deprecated for use Vectors. But Vectors are still around here as DefaulTableModel too. Thanks John and sorry for my english..
With the vector both add and get methods are synchronized.
You might have a case where you build a list once, and then want to READ from it from multiple threads. That should be safe with just the unsynchronized ArrayList, but to be safer you could wrap the list in an Collections.unmodifiableList. Then you won't need the overhead of synchronization on your get calls.
Very interesting video. I used Vectors way back in 1.2 or 1.3 but never bothered to find out how they are different than ArrayList. Thank you. Keep up the good work.
Awesome as always. I work as a Java dev but I still can find interesting and not-known topics in your videos.
Good to watch your videos!
Wow! John I have not idea about this concept, but now is clear. Thank you.
SIRRRRRR......U R Great... you solved my longlasting issue by vector class.
i was making a 2d style java game and usling LinkedList. when i skip level or in fast or sometime it stuck it always gave me error. linkedlist. it tried above code for sync, but did not work.
after watching your video, i changed it to vector . no issue now, no significant or noticable lagg or any issue that was facing and hitting head with codes and its technique OOP method.
Great.......
Thats a very good explaination. ArrayList has less time for execution but vector is high and Threads are high in Vector but less in ArrayList.
I love your videos!!! Learned something again I didn't know!
You can used synchronized in one of the threads. This synchronises in both threads which might not be necessary when there are 2 threads. N threads N - 1 synchronisations. If N is large you can synchronize all threads.
Thanks a lot for all of your information to the point content man.
It would be great to see videos on SOLID principles and Design Patterns from you.
Thank you very much John. You do teach really well.
Im going to use start and end to measure my code's time. TY
I love your videos, you really explain very well, greetings from Mexico city.
This is the best video I have seen on Vector. Thanks a lot
Thanks a lot John.
I’m really glad I found your channel, thank you for such quality content!
Vectors is one of the topic that always kind of confused me. Thanks for detail explanation
OMG - im suffering here with vectors for no reason at all...Thx for this excellent explanation
Great video. One suggestion I would give is to use Duration to measure time instead of System.currentTimeMillis() as it is not that reliable, specially when dealing with lots of data, the effect of CPU throttling and time leap will mess your count.
LocalDateTime with duration to measure the difference is better
Whole video summarized in a sentence:
Vectors are slower because unlike arraylists they are thread-safe so just use arraylists and if you have multiple threads use Collections.synchronizedList(arrayList).
Funny Thing is if i switch the first example around, adding to the vector is faster than adding to the arraylist.
Checked again with two ArrayLists and adding to the first datatype is always half the time than adding to the second one ^^
❤ your videos, thanks a mill. Please show up how you would create your own synchronized class.
Thanks for sharing about vectors asd arraylist , you demonstrated how arrayList performs poorly with multi threads if not synchronised.
what happens if parallelStreams are used?
Does it automatically gets wrapped into Collections.synchronized()
no idea if it has been covered, but explaining public, private, protected and package private might be a good idea. just a thought.
and in my opinion making some examples a little bit more complex might help for like a real world example. as extending some functionality might be tricky for learning developers.
also if possible, please stick to one IDE
swapping between intelli J and Eclipse can be mildly distracting. and an ide specific functionality is a pain if someone is using Eclipse and they wanna do something only available in Intelli J
other wise love your good work, very helpful
could we have a lesson on FUNCTIONS, BIFUNCTIONS, SUPPLIERS, CONSUMERS and other functional interfaces with a demo of passing them to methods etc :)
Hi, John! Can you make a video on Quarkus and GraalVM?
I have a quick question regarding the performance difference between Vectors and Arraylists, or more specifically with the synchronizedlist, if you create the synched list wrapper for your arraylist, does it only take that performance hit and start behaving comparably to a Vector in a threaded environment, or does it slow down the ArrayList when accessing it in a single thread also?
Sir kindly create complete video for Java . Which will be helpful for lot of beginners to understand what exactly java❤
Good video! One question: Aren't Vectors deprecated?
Hey John, love your vids! Will you ever make a video on thread pooling and asynch. programming?
Hello John, always appreciate your clear and concise way of explaining difficult JAVA concepts, can you please talk about Dynamic proxies when you get a chance? Thanks
ArrayList is fast because it is non-synchronized , Vector is slow because it is synchronized
Very good job. Best wishes to John.
Could you please make some video on Reactive Java , particularly project reactor.
Hello, awsome video as always, i learned so much from you. I wanted to ask if you could do a video about Http requests
Someone tell John we would really love an intro to springboot course from him, perhaps some 30 min crud app of some sorts. His videos helped me finally get the hang of recursion after reading hundreds of articles and numerous youtube videos later.
I'll let him know 😮
@@CodingWithJohn Lots of thanks.
Just wow! nice explanation
After so long....good to see it :)
The way you explain things is so nice.
I saw weird behaviours when testing... I ran it with Java 20, and consistently Vector was faster than ArrayList with a milion item, but with 10, ArrayList is faster again...
Hi,
Can you make a video about composition ?
thx a lot
Please, do more videos, I love them.
Me Gusta :)
Next video, maybe something about switch statement and how it evolved in Java?
Or maybe something about using debugger in most popular IDE's? That would be also extremely useful for beginners :)
Hello John! Please post more videos!! When I watch your explanations I don’t feel like a complete idiot who can never be a developer but the opposite!!!! It would be cool if you made some videos about patterns of programming or about spring framework or about microservises
Anyway whatever you do I love your content!)
Vectors in Java were initially implemented to be thread safe as the original philosophy in Java was to just do everything one way to fit every use case. It's the reason why every method is virtual and must be contained in a class, among other things.
By the way, the other data structure from the original Java version is Hashtable. It corresponds to the more useful HashMap.
It's also worth noting that Java also have a number of other concurrent data structures in the java.util.concurrent package, like BlockingDeque, ConcurrentHashMap, etc.
Hello , John
Ukraine is watching you 🇺🇦
You are the best Java-blogger I’ve ever seen)
in javaFX Application is an abstract class. In this abstract class there have some abstract methods which are overridden in main class which extends abstract Application class and also have static launch() method in abstract class Application. The launch() method calls from the main method in main class. Now how is it possible launch() method calls these abstract methods and for these calls overridden methods in main class are executes? please help to understand
Hi sir can you please do a video on Thread pools and executor service in Java?
can you please make a video on: encapsulation, inheritance, polymorphism, and abstraction... pleaseeeee
thank you man
Hi there. Is there some news on the Vector Api? When they will exit the incubation state? I put a lot of effort to use them in my program and they are devastating on some loads with CPUs that supports AVX512. My concern is that I'll need to rewrite everything for API changes when the APIs will exit the incubator state. I have some "development questions" on those APIs, are there a mailing list where to discuss about the use and the benefit of those APIs?
The thread experiment probably does not guarantee mutual exclusion and order of delivery, right? So, how does ArrayList and Vector behave on synchronized scenarios with semaphores, reentrant locks and so on...
Also, in the beginning you just printed out the static 1M integer value instead of printing the Collection object's size, but still good video, very informative, thanks.
Also: how dare you say ill things about Vector, what are you a pagan or an anarchist?
🧐
What about concurrent collection?
Haters gonna say the new updates are bad, but you can still use the old ones and also if you don't develop you will just get stuck in the past. I think most new things are optional and you don't have to use them, however it's always good to use both. I will continue to use the old hello world but I will also try out new things and learn the new update as well. Having additional knowlege will always give an advantage.
When using awt/swing parts of the api uses vector (probably because the api was written before the collections framework) and it's pretty annoying to be forced to use vectors in multiple places or copy a bunch of array lists into vectors.
I never see join() method, it's possible to make deadlock with it?
I'm running this code locally and the elements are being added to a vector about 2x faster than an arrayList (consistently). Could this be because I'm on an M series Mac with ARM architecture?
I used Vectors way back in Java 1.2 or maybe 1.3, after ArrayList I never looked back
Great video!
hello John, love your content. Can you make your course available on Udemy or LinkedIn ?
Your videos are gem
Hello John
I would like to see a real practical example of using the java collection framework.
I never understood the fundamentals of collection framework and if it is related to the database like mysql.
I am really struggling with the concept of database and data structures.
Please help 😢 SOS
You should use CopyOnWriteArrayList, not Vector.
why Arraylist is faster even in the single-threaded example?
Now compare vector and synchronized list (from Collections.)
Hello and thank you. Should we use Vector if we are just reading from List in multithreading mode? Is ArrayList is safe for reading in multithreading? Thanks in advance!
If it’s only accessed from one thread you do not need to synchronise, and if it’s accessed from multiple threads you may want to handle the synchronisation in the surrounding code to allow several operations to be atomic.
Alternatively there says there are constructs that are better suited to concurrency, such as a concurrent hash map
@@monishbiswas1966 thank you for reply
That was damn good info
This is perfect
I've used Vectors in C++. Considering where I come from, where things are supposed to safe instead of just fast, I may keep using Vectors in Java. At least when I don't get punished by a boss for doing so.
Can you make a multi-threading video like one thread need to create a image in dir with distinct name and another side the thread need to write a text in one file upto 2 Million in efficient way
I think there is a new Vector implementation in the coming JDK, I thought this video was about that new feature 😅😢
I'll have to check into that!
perfectly informative :)
can u explain JavaFX Basics? please
hahahaha the end was awsome, thanks man u r the best
could've extracted the single-threaded and multi-threaded benchmarks into separate functions taking a List instead of copy-pasting and renaming variables all over the place
TLDR: Vectors are synchronized, thus thread-safe and slower. ArrayLists are not synchronized, thus faster, but unsuitable for multi-threaded scenarios.
The only other situation is if you're using 3rd party code, and they force you to use Vector. Of course, you'd try to limit the use of Vector by copying into a Vector at the very last minute just before passing it as a parameter. If a Vector is returned, it may be useful to just put it into a List variable if you're not going to manipulate the elements in any way afterwards. If you are, still put it in a List variable, but consider if you need the thread safety. If not, then copy from the Vector into an ArrayList.
What's the font you use in the code editor?
Good Monday coffee waiting for breakpoints to trigger
Is this Vector the same as something something Vector API coming with the most recent Java version?
No, new vector api is about using SIMD processor instructions in a portable way.
awesome!!! JOHN
great vid
HEES BACK!!!!!!
One other difference: If you don't use the List interface, Vector has a lot of additional methods which are just confusing.